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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is clear. The description adds the instruction to include conversation for reproduction, which hints at a need for context but does not disclose further behavioral details like side effects or required authentication.

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?

Two concise sentences, front-loaded with purpose and a key usage hint. No fluff or redundant details.

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 description is incomplete for a 3-parameter tool with no output schema and 0% schema documentation. It only partial explains 'conversation', omitting the essential 'message' and 'context' fields, leaving the agent guessing how to provide them.

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 must compensate. It only mentions the 'conversation' parameter, leaving 'message' (the actual report content) and 'context' unexplained. This is insufficient for an agent to correctly fill all 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 purpose: report a bug, missing feature, or feedback, using a specific verb ('report') and resource ('bug/feedback'). It is distinct from sibling tools which are unrelated (auth, billing, version).

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 usage—when a bug or feedback is encountered—but gives no explicit guidance on when not to use or alternatives. It mentions including conversation for reproduction, which hints at context but lacks exclusions or prerequisites.

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