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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description does not contradict these. It adds minimal behavioral context, such as the need for recent messages for reproduction. However, it does not disclose any side effects, permissions, or response behavior beyond what annotations imply. The bar is lower due to annotations, so a score of 3 is appropriate.

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 primary purpose, and every sentence adds value. It is concise without extraneous information, making it efficient for an agent to parse.

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 with three parameters and no output schema, and annotations cover safety traits. However, the description leaves gaps: it does not explain what the response looks like, does not clarify the 'context' parameter, and introduces a type inconsistency for 'conversation.' Given these gaps, the description is minimally adequate but not 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?

With schema description coverage at 0%, the description must compensate but only partially does. It explains the purpose of the 'conversation' parameter (for reproduction) but incorrectly calls it an 'array' while the schema types it as a string, which could mislead agents. It does not explain the 'context' parameter's purpose. This incomplete compensation and type mismatch warrant a low score.

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 clearly states the tool's purpose with a specific verb 'Report' and resources 'bug, missing feature, or send feedback.' It also mentions including the conversation array for reproduction, which adds practical context. However, it does not explicitly differentiate from sibling tools, though the sibling list (authenticate, marketplace, etc.) makes the distinction obvious.

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 for when to use the tool: to report a bug, missing feature, or send feedback. It also gives usage guidance on including the conversation array for reproduction. It does not mention when not to use it or alternatives, but the tool's purpose is sufficiently distinct from siblings.

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