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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, indicating this is a non-destructive write operation. The description adds minimal behavioral context beyond describing the reporting action itself. It doesn't mention side effects, response expectations, or authentication needs. With annotations present, the bar is lowered, but the description could have added more context (e.g., that reports are submitted asynchronously). Score 3 reflects adequate but not rich disclosure.

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, front-loaded with the primary purpose and the key usage instruction. Every sentence serves a purpose, with no fluff or repetition. It is well-structured and concise.

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 tool with 3 parameters (1 required), no output schema, and no nested objects, the description is mostly complete. It covers the main action and the critical conversation parameter. It doesn't elaborate on the return value or the context parameter, but these are relatively minor gaps given the tool's simplicity and the presence of annotations. A dedicated effort to explain that context is optional additional information would push it to 5, but as is, it's 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 schema description coverage at 0%, the description must compensate for parameter meanings. It explicitly explains the 'conversation' parameter ('Include the conversation array with recent messages for reproduction'), which adds value. However, it does not explain the optional 'context' parameter or expand on 'message' beyond the schema. This partial compensation yields a baseline score of 3.

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: 'Report a bug, missing feature, or send feedback.' It specifies the verb (report) and the resource (bug/feature/feedback), which distinguishes it from sibling tools like authenticate, marketplace, or show_version. The added instruction about the conversation array reinforces its purpose.

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 implies when to use the tool (when there is a bug or feedback) and provides specific guidance to include the conversation array. However, it does not explicitly mention alternatives or when not to use it, but the sibling tools are clearly distinct in scope, so exclusion is less critical. Slight deduction for lack of explicit when-not guidance.

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