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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds useful behavioral facts on top: default page size of 30, a hard max of 100, and that `count` reflects all matches rather than the page. It doesn't discuss pagination mechanics (offset/cursor) for retrieving beyond 100, which is the one remaining gap.

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 sentences, front-loaded with the scope and then the navigation hints; every clause carries routing value. The field enumeration is a bit listy but pays for itself given there is no output schema.

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?

No output schema exists, and the description compensates by naming the fields returned plus the `count` semantics, so an agent knows what it will get. Combined with the sibling routing and page-size limits, nothing needed to call this correctly is missing.

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 every parameter is already documented with defaults and constraints in the schema. The description's only parameter-adjacent addition is the '30 by default, max 100' note, which the `limit` schema field already states verbatim. Baseline 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?

Specific verb plus resource ('List inbox conversations') immediately scoped as 'direct messages from every connected network plus the website chat', and it enumerates the returned fields. It also explicitly carves out sibling territory (list_tickets for tickets alone, list_comments for public comments), so the agent can distinguish it without opening any schema.

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?

Explicit routing to the follow-up tools: 'Read one thread with get_conversation (the id), reply with send_message and triage with update_conversation'. It also states what this tool is not for, naming list_tickets and list_comments as the alternatives for those resource types.

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