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

Annotations already indicate idempotent (idempotentHint: true) and non-destructive (destructiveHint: false). The description adds behavioral context by instructing to include the conversation array for reproduction, which clarifies the tool's reliance on conversation data. It does not contradict the annotations—the idempotency claim is consistent with a report action (though duplicates could be a concern, the annotation is authoritative).

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 short sentences. It front-loads the purpose immediately and adds a single critical usage hint. There is no fluff or redundancy, making it efficient.

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?

With no output schema, the description should explain what the tool returns or the outcome of the action. It does neither. Additionally, it only partially documents parameters, leaving 'message' and 'context' undefined. Given the tool's simplicity, it still lacks essential return-value info and parameter coverage, making it incomplete for an agent to use confidently.

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?

Schema description coverage is 0%, so the description must compensate. It explains the 'conversation' parameter (include recent messages for reproduction) but does not clarify 'message' (though it's implied as the report content) or 'context' (which has a default but no explanation). This leaves two of three parameters ambiguous.

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.' This is a specific verb (report) with clear resources (bug, missing feature, feedback), and it distinguishes itself from sibling tools like show_version or authenticate by its focus on issue reporting.

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 provides clear context for when to use the tool (when a bug, missing feature, or feedback is encountered) and mentions a required action (including the conversation array for reproduction). However, it does not explicitly name alternatives or state when not to use it, but the sibling tools are so distinct that the usage context is unambiguous.

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