get_conversations_bulk

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description still adds real value: the fan-out/concurrency implementation, the 50-ID ceiling, and the returned field set. It stops short of stating what happens on partial failure or invalid IDs in a batch, which matters for a 50-item fan-out.

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 what it does and what it returns, then the limit, then the workflow. Dense but zero filler; each clause carries an actionable fact.

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?

Even with no output schema, the description enumerates the return shape ({ID, summary, ts, capturedVariables, userName, origin}) and gives both the batching constraint and the surrounding workflow. An agent has everything needed to call it correctly in a bulk-audit scenario.

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 the baseline is 3, but the description adds the practical bound ('Max 50 IDs per call — chunk larger audits') that the schema's '1–50' note doesn't operationalize, and characterizes the payload as lean summaries rather than full conversations.

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+resource with scope: 'Fetch lean summaries for many conversation IDs in one call'. It distinguishes itself from get_conversation ('do NOT loop get_conversation') and from list_conversations (which supplies the IDs), so an agent can route correctly without opening either 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?

Gives an explicit workflow ('list_conversations with cursor to collect IDs, then this tool'), an explicit anti-pattern ('do NOT loop get_conversation'), and a hard operating limit with a remedy ('Max 50 IDs per call — chunk larger audits'). Nothing is left to inference.

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