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

The annotations provide safety signals (idempotentHint=true, destructiveHint=false) but the description adds little behavioral context. It explains that the conversation array is needed for reproduction, but does not disclose whether the report creates a permanent entry, sends data externally, or what the user should expect after calling the tool.

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 one concise sentence that front-loads the core purpose and then complements it with a specific, actionable detail. No filler or redundant content.

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 is relatively simple, and the description covers the main use case. However, missing parameter semantics and lack of information about the conversational payload format mean the description is only minimally sufficient for a 3-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 description coverage is 0%, so the description carries the burden of explaining parameters. It only hints at the 'conversation' parameter by mentioning the conversation array. The 'message' and 'context' parameters are not described in the text, leaving the agent to infer their meanings from the schema alone.

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 uses specific verbs ('Report', 'send feedback') and clearly defines the resource/action scope as bugs, missing features, and feedback. It distinguishes itself from all sibling tools, which are unrelated to bug 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?

It states when to use the tool: 'Report a bug, missing feature, or send feedback.' It also gives a concrete usage tip about including the conversation array for reproduction. It does not mention alternatives or exclusions, but such guidance is not necessary 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.