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

Annotations already indicate this is a non-read-only, idempotent operation. The description adds the instruction to include the conversation array for reproduction, which is helpful, but it doesn't disclose what happens after reporting (e.g., ticket creation, confirmation) or any side effects beyond the 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?

Two concise sentences, front-loaded with the tool's purpose, no redundant wording.

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 description gives the core purpose and one key parameter use, but lacks information about return values or post-submission behavior (no output schema). The 'context' parameter is unexplained, and the 'conversation' type discrepancy (array vs string) isn't clarified. For a simple tool it's adequate but incomplete.

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?

The description clarifies the 'conversation' parameter as an array containing recent messages, which is not explained in the schema. However, 'context' and 'message' are not explicitly defined, leaving their semantics to inference given the tool's purpose.

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 specific verb 'Report' and lists three resource types: bug, missing feature, feedback. This clearly distinguishes it from sibling tools, none of which relate to 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 implicitly indicates when to use it (when there's a bug or feedback) and provides explicit guidance to include the conversation array for reproduction. However, it doesn't explicitly mention alternatives or exclusions, though no near alternatives exist.

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