Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys the core mutation and that the session must already exist, but it does not disclose what happens if chatId is invalid, whether messages are appended in order, whether the session is modified in place, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with a front-loaded action and no filler. It is concise, direct, and easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple three-parameter append operation, and the description plus schema covers the basic invocation. However, with no annotations and no output schema, the lack of return behavior, ordering semantics, and error handling leaves a moderate completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents chatId, messages, and projectId. The description adds little beyond the word 'existing', which weakly reinforces that chatId must refer to a previously created session.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Append') and a distinct resource ('messages to an existing chat session'). This clearly separates it from sibling tools like save_chat_session, get_chat_session, and list_chat_sessions, and the qualifier 'existing' adds useful scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used to add messages to an already-created chat session, but it does not explicitly state when to use this tool versus save_chat_session or other chat-related siblings. No alternatives or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.