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

The annotations already declare idempotentHint=true and destructiveHint=false, indicating a non-destructive, repeatable operation. The description adds the reproduction context for the conversation input but does not disclose additional behaviors like submission targets, response format, or rate limits. No contradiction with 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 two sentences, no fluff. It front-loads the purpose before adding a usage detail.

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?

For a simple reporting tool, the description covers the core purpose and a key reproduction requirement. However, it doesn't mention expected response or what `context` is for, and it relies on annotations for safety information. Overall adequate but not exhaustive.

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?

The schema provides no descriptions for any of the three parameters. The description explicitly instructs to include the conversation array for reproduction, clarifying `conversation`, and implies `message` carries the report. However, `context` is unmentioned, and `conversation` is called an array while the schema types it as a string, leaving some ambiguity.

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 states 'Report a bug, missing feature, or send feedback,' clearly specifying the action and resource. This distinguishes it from sibling tools, none of which relate to reporting.

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 first sentence makes the use case obvious. The second sentence adds specific guidance: 'Include the conversation array with recent messages for reproduction.' No alternatives are mentioned, but none are needed given the distinct purpose.

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