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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the description adds little behavioral insight beyond 'reporting' and the reproduction instruction. It does not contradict annotations but also does not elaborate on side effects, return details, or what happens with the data.

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 sentence that front-loads the purpose and includes a critical usage hint about the conversation array. No redundant words or 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?

The tool has 3 parameters and no output schema. The description covers the essential purpose and mentions the most important parameter (conversation), but does not state what the tool returns or any additional context like authentication or expected response. For a simple reporting tool, it is adequate but not complete.

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 0% schema description coverage, the description must compensate. It explains 'conversation array' as containing recent messages for reproduction, and implies 'message' is the content of the report, but 'context' is not explained. This gives partial value but falls short of fully clarifying all three parameters.

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 the verb 'Report' and the resources 'bug, missing feature, or send feedback,' making the tool's purpose unmistakable. It is distinct from sibling tools like 'connect' or 'show_version' since none are related to reporting issues.

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 implies when to use the tool ('when reporting a bug, missing feature, or feedback') but does not explicitly contrast with alternative tools or state when not to use it. It includes a specific instruction to include the conversation array, which is a parameter-level guidance rather than usage context.

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