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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds a real behavioral fact beyond that — the caller needs read scope — but says nothing about ordering, pagination, or volume limits implied by 'all messages'.

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?

Two short sentences, front-loaded with the action and followed by the auth prerequisite; no filler. It is terse to the point that useful detail (ordering, result size) is omitted, but nothing present is wasted.

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 one-parameter read tool with full schema coverage and safety annotations, the core is covered. It falls short on what 'all messages' returns for a long conversation (pagination, ordering, caps), and there is no output schema to fall back on.

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% with a single documented uuid parameter ('conversation ID'), so the schema carries the semantics. The phrase 'in a conversation' merely echoes the id parameter without adding format or sourcing detail, so the baseline of 3 applies.

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?

States a specific verb+resource: retrieve all messages belonging to a conversation, with the scope of the read made explicit by 'all messages'. It does not, however, distinguish itself from nearby siblings such as get_campaign_chat_messages or list_pending_messages, so an agent must infer the boundary from names alone.

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 only guidance is a prerequisite ('requires read scope'), not a when-to-use rule. Nothing says when to pick this over get_campaign_chat_messages or list_pending_messages, nor whether a conversation ID must be obtained first via get_conversation.

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