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

Annotations already indicate non-destructive and idempotent behavior. The description adds the need to include conversation context but does not elaborate on authentication, rate limits, or what happens after submission. It neither contradicts nor substantially enriches the annotation information.

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, no filler. The first sentence immediately states the purpose, the second provides key usage instruction. Every word is functional.

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 sufficiently covers what the tool does and what information to provide. It could mention if a confirmation response is sent, but overall it is complete enough for an agent to use correctly.

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 coverage is 0%, so the description must compensate. It explains the conversation parameter's purpose ('recent messages for reproduction') but does not clarify 'context' or 'message' beyond their names. This partial coverage raises it from baseline 1 to 3.

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 explicitly states three use cases (bug, missing feature, feedback) with a clear verb 'report' and identifies the resource. It distinguishes from all sibling tools, which are unrelated to bug 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?

Advises to include the conversation array for reproduction, which is helpful context. While it doesn't explicitly exclude alternative uses or state when not to use, the sibling set contains no other feedback tools, so the guidance is clear enough.

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