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

Annotations already declare idempotentHint=true and destructiveHint=false, setting the safety profile. The description adds that data (conversation) should be included 'for reproduction,' implying the report is sent externally, but doesn't elaborate on destination, rate limits, or side effects. It doesn't contradict the annotations, but also doesn't add substantial behavioral depth beyond what the annotations already imply.

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 that immediately states the purpose and then gives a concrete, actionable instruction. There is no redundancy or filler—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?

For a simple reporting tool with only three parameters and no output schema, this description is nearly complete. It covers the core purpose and the most non-obvious parameter (conversation). It could mention what happens after submission (e.g., a ticket is created), but given the simplicity, the current level is adequate.

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 was expected to compensate by explaining parameters. It only mentions 'conversation array' for reproduction, leaving 'message' (the required parameter) and 'context' completely undocumented. The agent can guess from names, but the description doesn't add enough value above that.

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 names three explicit targets (bug, missing feature, feedback), clearly distinguishing it from sibling tools like authenticate or marketplace. It's immediately obvious what this tool does and when to use it.

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 clearly indicates when to use it ('Report a bug, missing feature, or send feedback') and provides a concrete tip about including the conversation array. However, it doesn't explicitly contrast with alternatives or state when not to use it, which prevents a perfect score.

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