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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds context about including the conversation for reproduction, which is useful. Yet it doesn't disclose potential side effects, whether feedback is sent externally, or any rate limits, but the safety profile is partially covered by annotations.

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?

Two sentences with no wasted words. The instruction about the conversation array is directly useful and not redundant with the schema.

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 tool is relatively simple, but the description could be more complete: it lacks explanation of the 'message' and 'context' parameters, and there is no mention of what happens after submission. The conversation type mismatch adds a slight ambiguity. Despite this, it covers the core usage sufficiently for a low-complexity tool.

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?

With schema description coverage at 0%, the description must compensate. It explains the 'conversation' parameter's purpose but leaves 'message' and 'context' undefined. Also, the description calls it a 'conversation array' while the schema declares it as a string, which is a subtle mismatch.

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 with a specific verb ('Report') and the resource (bug, missing feature, feedback). It distinguishes from unrelated sibling tools like 'authenticate' and '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?

It provides clear context on how to use the tool (include conversation array) and the general case for reporting bugs/feedback. However, it doesn't explicitly mention when not to use it or name alternative tools, but the siblings are unrelated, so this is acceptable.

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