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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the description's job is lighter. It adds genuine value by disclosing return content and the non-obvious AI behavior (ai_paused_until while a teammate's reply pauses it), which the structured fields do not convey.

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?

Front-loaded with the core action, then a dense but purposeful enumeration of returned fields, capped by a short routing sentence. Every clause maps to a distinct field or usage cue, with no filler.

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?

There is no output schema, so the description appropriately carries the burden of describing what is returned, and it does so comprehensively. Combined with readOnly annotations and a fully covered input schema, an agent has what it needs to call it correctly.

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 both parameters are fully documented in the schema (including 404/403 error semantics), making the baseline 3. The description only incidentally relates to conversation_id via the list_conversations routing hint and adds no syntax or format detail beyond the schema.

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 and resource ('Get one conversation of an agent') and then enumerates the fields it returns, which distinguishes it from siblings like get_conversation_message and list_conversations. It does not explicitly name a sibling it is not, so it stops short of a 5.

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 closing line 'Get its id from list_conversations' gives an actionable prerequisite that routes the agent to the right sibling for obtaining the id. There are no explicit when-not-to-use conditions or exclusions, so it is clear context rather than a 5.

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