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

The description matches the readOnlyHint annotation by saying 'Read', and no side effects are mentioned. However, it does not add rich behavioral context beyond the annotations, such as error conditions, data limits, or ordering guarantees other than 'chronological'.

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, focused sentence that leads with the verb and resource. It contains no redundant phrasing or unnecessary details, making it highly concise and well-structured.

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?

While an output schema exists, the description leaves key aspects unexplained, such as the meaning of 'recent' (time window vs. count) and the purpose/behavior of the 'limit' parameter. This makes the tool incomplete for an agent trying to invoke it correctly without additional context.

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 0%, and the description provides no explanation of the 'limit' or 'projectId' parameters. Since coverage is extremely low, the description was expected to compensate by explaining parameter meaning, but it does not.

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 clearly states the verb 'read', the resource 'project chat messages', and the scope 'recent... in chronological order'. It is distinguishable from sibling tools like send_chat_message or list_comments based on the resource and action.

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 usage for reading chat messages but does not explicitly contrast with alternatives like list_comments or send_chat_message. There is no 'use this when' or 'instead of' guidance, so the agent must infer the appropriate context from the resource name.

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