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

Annotations already cover idempotentHint=true and destructiveHint=false, and the description adds 'for reproduction' as context for the conversation parameter. However, it doesn't describe side effects like ticket creation, sending the report, or any rate limits. No contradiction with 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?

The description is a single, front-loaded sentence with no redundancy: it states the purpose and then a concrete reproduction instruction. Every word earns its place.

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 simple and the description covers the core purpose and an important reproduction guideline. However, it omits meaning for 'message' and 'context', and with no output schema or return-value description, the agent may be uncertain about expected behavior.

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 0% schema description coverage, the description must compensate, but it only explains the conversation parameter, and even that lacks format details (schema says string, while description says 'array'). The required 'message' parameter and optional 'context' field are left undifferentiated.

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 the action verb 'Report' with clear objects ('bug, missing feature, or send feedback'), making the tool's purpose immediately obvious. It also differentiates from sibling tools like marketplace and show_version, which serve unrelated functions.

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 clearly states when to use the tool: to report a bug, missing feature, or feedback. It also gives a specific usage instruction (include conversation array for reproduction), though it does not explicitly mention alternatives or exclusions.

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