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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds behavior beyond them: fan-out GETs with concurrency, a hard 50-ID cap requiring chunking, and the exact return shape. It does not state what happens to unknown/missing IDs or whether there are rate limits that make very large audits risky, which would be the remaining useful disclosure.

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?

Three tight sentences, front-loaded with the purpose, then the return shape, then the cap and workflow. Slightly telegraphic abbreviations ('per convo', 'ts', 'fan-out GETs') cost a little clarity, but there is 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?

With no output schema, the description correctly lists the returned fields, and it covers the batching constraint and the collection workflow. It leaves out error/partial-result behavior and auth requirements, minor gaps for a read-only two-parameter tool.

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 coverage is 100%, so `agentId` and `convoIds` are already documented, and the schema itself carries the 1–50 bound. The description's 50-ID limit adds mild reinforcement but no new syntax or format 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 and resource with scope: 'Fetch lean summaries for many conversation IDs in one call'. It explicitly contrasts itself with `get_conversation` ('do NOT loop get_conversation') and with `list_conversations`, so an agent can distinguish it from siblings without opening schemas.

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?

Gives an explicit workflow: use `list_conversations` with a cursor to collect IDs, then call this tool. It names the anti-pattern to avoid (looping `get_conversation`) and states the batching rule ('Max 50 IDs per call — chunk larger audits').

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