docs(core): add message-type-specific documentation for message name
fields
#32469
+98
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the name field documentation in v1 messages to provide message-type-specific guidance instead of generic descriptions. The current documentation incorrectly presents the field as purely "human-readable" when it serves critical functional purposes that vary by message type.
ToolMessage.name
is effectively required by most providers despite being typed asOptional[str]
AIMessage.name
is critical for multi-agent systems but optional for single-agent scenariosExamples
langchain-openai
AIMessage.name
name
when present on a messageToolMessage.name
langgraph-supervisor-py
AIMessage.name
langchain-google
FunctionResponse
objectslangchain-community
message.name
for tool/function calling