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

Annotations already provide idempotentHint=true, readOnlyHint=false, and destructiveHint=false. The description adds a meaningful behavioral instruction: the conversation array is to be included for reproduction. However, it doesn't disclose what happens after submission, whether the report is sent externally, or how idempotency is maintained.

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 contains only two sentences, with the first giving an immediately clear purpose and the second giving a practical instruction about the conversation parameter. Every word earns its place, and it is appropriately sized for this simple tool.

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 feedback-reporting tool, the purpose and one special parameter are conveyed well, and annotations cover behavioral constraints. But the description lacks any explanation for the 'context' parameter, doesn't mention expected feedback after submission, and leaves the 'conversation' array formatting entirely to the user's imagination.

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 no property descriptions (0% coverage), so the description must compensate. The only parameter it meaningfully explains is 'conversation' ('recent messages for reproduction'). The required 'message' parameter is only inferable from the tool's purpose, and 'context' is completely unexplained.

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 uses a specific verb ('Report') and lists a clear resource scope ('a bug, missing feature, or send feedback'). This clearly differentiates it from sibling tools like authenticate, connect, and show_version, establishing its unique purpose.

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 clearly indicates it is for bug reporting, feature requests, and feedback—contexts where it should be used. It does not explicitly mention when not to use it, but the sibling list shows no overlapping alternatives, so the usage context is clear without needing exclusions.

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