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

Annotations indicate the tool is idempotent and non-destructive, so the description adds limited behavioral detail. It mentions including conversation for reproduction, hinting at context usage, but does not explain side effects or outcomes, keeping transparency modest.

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 concise sentences with no extraneous words. It efficiently communicates the core action and a key requirement, making it easy to parse.

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 reporting tool, the description is largely sufficient: it states purpose and input guidance. However, it omits details like expected return values or error handling, but given the lack of output schema and low complexity, this is acceptable.

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 provides no descriptions, but the description explains the purpose of the 'conversation' parameter (to aid reproduction) and implies 'message' is the content of the report. It does not clarify 'context', but this partial coverage improves understanding.

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: reporting bugs, missing features, or feedback, which is a distinct function compared to sibling tools like authenticate or show_version. It also specifies a required action (include conversation) that clarifies its role.

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 (for bug reports or feedback) but does not explicitly contrast with alternatives. It provides guidance on how to use it (include conversation array), which is helpful though not exhaustive for a usage decision.

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