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

Annotations already set readOnlyHint=true and destructiveHint=false, and the description reinforces the read-only nature by describing data retrieval. It adds behavioral context about the fallback logic and report selection, which is beyond the annotations.

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?

The description is a single dense sentence, reasonably concise but includes an internal tag '[content_fetch]' that may not be meaningful to an agent. The core logic is front-loaded, but the tag reduces clarity.

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?

Given an output schema exists and annotations are present, the description explains the core algorithm appropriately. However, it omits details on how 'offset' and 'brief_ids' influence results and does not describe the output format, leaving moderate gaps.

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?

With schema description coverage at 67%, two parameters have descriptions while 'offset' lacks one. The description only mentions 'conversation_ids' and does not explain 'offset' or 'brief_ids' beyond what schema provides. This is adequate but not enhanced.

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?

The description clearly states it fetches a 'compact report body' per conversation, specifying the fallback hierarchy (Brief->Summary->Standard) and the selection criterion ('first completed non-empty type=0 report'). This distinguishes it from sibling tools like get_summaries or get_transcripts.

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 description does not provide explicit guidance on when to use this tool versus alternatives. It implies usage for brief reports but lacks when-not-to-use scenarios or comparisons with sibling tools such as get_conversations or get_summaries.

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