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

Annotations already convey idempotency and non-destructiveness. The description adds the requirement to include the conversation array for reproduction, which is useful context, but it doesn't disclose any other behavioral aspects (e.g., side effects, return behavior). Given the annotation coverage, this is adequate.

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—two sentences that front-load the action and then add a key usage directive. No fluff or unnecessary details.

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?

Given the tool's simplicity (3 params, no output schema), the description covers the core function and a critical usage detail (conversation array). It doesn't explain every nuance, but it's sufficient for the complexity level.

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 parameter meaning. It explains 'conversation' as an array of messages, but does not clarify 'message' or 'context'. However, 'message' is self-evident as the bug report text, and 'context' is partially implied. Partial compensation.

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 identifies the tool's purpose: reporting bugs, missing features, or feedback. It uses a specific verb ('Report') and resource ('bug, missing feature, or send feedback'), and distinguishes it from all sibling tools, none of which handle 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?

It states the tool is for reporting bugs/feedback, and instructs to include the conversation array for reproduction. While it doesn't explicitly mention alternatives or when-not-to-use, the sibling tools are unrelated, so usage context is clear.

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