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

Annotations indicate idempotentHint and non-destructive behavior, and the description adds context by explaining the inclusion of conversation for reproduction. It does not contradict the annotations and gives useful insight into expected input handling.

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, consisting of two clear sentences. It efficiently conveys the purpose and a key usage hint without unnecessary elaboration.

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 gives enough context for a reporting tool, including what to report and the recommendation to provide conversation context. Since there is no output schema, it does not need to explain return values, and the description is reasonably complete for its intended function.

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 description explicitly mentions the conversation parameter ('Include the conversation array with recent messages for reproduction'), but does not explain the 'context' parameter at all and only implicitly suggests that 'message' contains the report content. With a low schema coverage, the description does not sufficiently compensate for the undocumented 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 tool's purpose: 'Report a bug, missing feature, or send feedback.' It uses a specific verb and resource, and it is distinct from sibling tools like authenticate, connect, 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 indicates when to use the tool (for bug reports, feature requests, feedback) and provides guidance to include the conversation array for reproduction. It does not explicitly contrast with alternatives, but the sibling tools are unrelated, making the usage context clear.

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