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

The description claims a read operation, while the annotation declares readOnlyHint=false, which is a direct contradiction. Beyond this inconsistency, it omits any disclosure of pagination behavior, scope side effects, or what happens when the limit is reached.

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 two short sentences with no waste, and the primary action is front-loaded. It is efficient, though it could have used its brevity budget to include more useful detail.

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?

For a read tool with three parameters, no output schema, and 0% parameter description coverage, the description is insufficient. It omits pagination semantics, return format, and any behavior beyond the scope requirement, leaving critical gaps for correct invocation.

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?

All three parameters have 0% schema description coverage, and the description provides no explanation for 'limit', 'before_id', or 'conversation_id'. It only implies conversation context, leaving the agent to guess the role of each parameter.

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 ('Read') and resource ('messages in a conversation'), which distinguishes it from sibling tools like send_message and list_conversations. It does not explicitly name an alternative sibling, but the core operation is unambiguous.

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 includes a prerequisite ('Requires the chat:read scope') but gives no guidance on when to use this tool versus alternatives like list_conversations or send_message. Usage is only implied by the tool name and context.

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