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

With idempotentHint=true and destructiveHint=false annotations, the description adds useful context by specifying that the conversation array should be included for reproduction. This goes beyond the annotations' implicit hints, explaining a behavioral expectation without contradiction.

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, concise sentence that front-loads the purpose and then provides a key usage instruction. Every word earns its place with no fluff or repetition.

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 feedback tool with three parameters and no output schema, the description adequately informs the agent what to do and one key detail (conversation array). It's complete enough for the agent to execute successfully, though a bit more detail on expected outcome could improve it slightly.

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 explicitly explains the 'conversation' parameter's purpose, and 'message' is self-evident from the verb 'report'. However, the 'context' parameter is not described, leaving ambiguity. Partial compensation only, so a score of 3 is appropriate.

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 verb 'report' and the resources 'bug, missing feature, or send feedback', distinguishing it from sibling tools like authenticate or connect. It explicitly tells the agent what action to take and the scope.

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 instructs to include the conversation array for reproduction, providing clear context on how to use the tool. However, it doesn't explicitly state when not to use it or mention alternatives, though no direct alternatives exist among siblings. The guidance is sufficient for basic usage.

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