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

Annotations already indicate non-read-only, non-destructive, and idempotent behavior. The description adds useful context by instructing to include the conversation array for reproduction, which is not covered by annotations. This provides additional behavioral guidance beyond the safety profile.

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, front-loaded with the primary action ('Report a bug...') and no filler. Every word contributes to understanding the tool's purpose and key 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 bug-reporting tool with annotations and no output schema, the description is largely complete. However, it does not clarify the 'context' parameter or the JSON-string format of 'conversation' (schema says string, description says array), which could lead to minor invocation confusion.

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 has 0% parameter description coverage. The description explains the 'conversation' parameter's purpose ('Include the conversation array with recent messages for reproduction') and implicitly covers 'message' as the bug/feedback content, but does not explain 'context'. This leaves a gap for one of three parameters, so the description only partially compensates for schema gaps.

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 'Report a bug, missing feature, or send feedback' with a specific verb and resource, distinguishing it from all sibling tools which are financial operations. The title 'Report Bug' and description align perfectly.

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 provides clear context for when to use the tool (reporting issues or feedback) but does not explicitly mention alternative tools or exclusions. Since no sibling tool handles bug reporting, the usage context is unambiguous.

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