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

Annotations already provide readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds the 'for reproduction' rationale for including conversation data, but it does not disclose whether the report is transmitted externally, stored, or whether duplicate reports are possible despite the idempotency hint.

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 short sentences with the purpose front-loaded and no filler. Every phrase earns its place, and the key usage instruction is presented immediately after the purpose.

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 tool with no output schema, the description covers the core purpose and the most important reproduction instruction. However, it leaves message and context semantics unspecified and does not mention any response behavior, making it minimally complete rather than thorough.

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 for the undocumented parameters. It explains the purpose of the conversation parameter (recent messages for reproduction) but calls it an 'array' while the schema types it as a string, and it does not clarify the required message parameter or the optional context parameter.

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 names three concrete resources: a bug, a missing feature, and feedback. It clearly distinguishes this tool from the unrelated flightradar and authentication siblings by establishing it as the user-reporting channel.

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 a concrete usage instruction: include the conversation array with recent messages for reproduction. It does not explicitly state when not to use the tool or name alternatives, but no sibling tool serves a similar reporting purpose, so this is adequate.

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