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

Annotations already indicate the tool is not read-only, not destructive, and idempotent, so the description doesn't need to restate those. However, it adds minimal behavioral context beyond the parameter instruction; it doesn't disclose what happens after a report is submitted, such as ticket creation or data handling.

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 sentences long, front-loaded with the core purpose, and contains no filler or redundant restatements of the tool name. Every sentence adds value.

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 tool with three parameters and no output schema, the description is mostly complete: it states the purpose and provides the key usage hint about the conversation array. The unexplored 'context' parameter and lack of any post-submission behavior note keep it from being fully complete.

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 meaningfully clarifies the 'conversation' parameter ('recent messages for reproduction') and implies 'message' is the bug/feedback text, but it does not explain the 'context' parameter at all, leaving a gap.

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') with clear objects ('a bug, missing feature, or send feedback'), making the tool's purpose immediately recognizable. It also distinguishes this tool from siblings like authenticate, marketplace, and show_version, which serve different 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 provides clear context: use this tool to report bugs, missing features, or feedback. It also gives explicit guidance to include the conversation array for reproduction, but does not mention when not to use it or name alternative tools for related tasks.

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