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

Annotations already provide safety information (idempotentHint=true, destructiveHint=false, readOnlyHint=false). The description adds minimal behavioral context beyond this, such as the need to include a conversation array for reproduction, but does not disclose side effects (e.g., data sent externally), response behavior, or prerequisites like authentication. It adds some value but does not fully enrich the behavioral picture.

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 contains no filler. It efficiently conveys the core action and a key usage detail. Every sentence contributes meaningful information.

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 tool with 3 parameters, no output schema, and no enums, the description is fairly complete in conveying purpose and the conversation parameter, but it leaves the 'context' parameter unexplained and says nothing about what happens after reporting. It is adequate for a simple tool but has clear gaps in parameter coverage and behavioral outcomes.

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. It explains the 'conversation' parameter ('recent messages for reproduction') and implicitly clarifies 'message' as the reported text, but it completely omits the 'context' parameter. This leaves one of three parameters semantically undocumented, so the description only partially compensates for the schema coverage 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 clearly states the tool's purpose with a specific verb ('Report') and explicit resources ('bug, missing feature, or send feedback'). This clearly distinguishes it from all sibling tools, which are unrelated (e.g., authenticate, connect, marketplace). The purpose is immediately understandable and unambiguous.

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: whenever the user wants to report a bug, request a feature, or give feedback. While it does not explicitly mention alternatives or exclusions, the sibling list contains no similar reporting tool, so the usage context is evident. The lack of explicit 'when not to use' guidance prevents a 5.

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