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

Annotations already cover idempotent, non-read-only, and non-destructive behavior. The description adds the requirement to include the conversation array, but does not mention side effects, potential errors, or permissions. Given annotations exist, the description provides minimal additional transparency.

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 concise and well-structured: two sentences clearly state the purpose and an important usage detail. No superfluous 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?

For a bug reporting tool, the description is reasonably complete: it states what to do and what to include. It does not describe output (no output schema), but that is acceptable. It lacks explicit guidance on when to use versus alternatives, which is a minor gap.

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 has three parameters (context, message, conversation), but the description only explains 'conversation' ('Include the conversation array...'). It does not explain what 'context' or 'message' mean, despite 'message' being required. This low coverage requires more explanation from the description, which is lacking.

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 tool's purpose: 'Report a bug, missing feature, or send feedback.' It also gives a specific instruction on including the conversation array, making it distinct from sibling tools like authenticate or show_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 when to use the tool (to report bugs/feedback) and provides an instruction on what to include. However, it does not explicitly contrast with alternatives or state when not to use it, so it falls short of being fully explicit.

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