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

Annotations cover readOnlyHint, destructiveHint, and idempotentHint, so the basic behavioral safety is already declared. The description adds useful context that the conversation array is needed for reproduction, but it does not disclose potential side effects such as external data transmission, which would be relevant for a 'send feedback' action.

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?

Two sentences, front-loaded with the tool's purpose followed by a practical usage hint. There is no redundant wording or unnecessary detail.

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 three-parameter tool with no output schema and unrelated siblings, the description provides enough guidance to invoke it correctly: it names the report types, suggests including the conversation array for reproduction, and the schema clarifies required fields. The only minor gap is the undocumented context parameter, which has a default value and is likely optional.

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 carry parameter meaning. It partially does: 'conversation array with recent messages' clearly maps to the conversation parameter, and the first sentence implies message contains the bug/feature/feedback text. The context parameter, however, is not explained or even mentioned.

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 a specific verb ('Report') plus the target resources ('a bug, missing feature, or send feedback'), making the tool's purpose unmistakable. This clearly distinguishes it from unrelated sibling tools like authenticate, connect, marketplace, and show_version.

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 clearly states when to use the tool: for reporting bugs, missing features, or feedback. It also gives an actionable instruction to include the conversation array with recent messages for reproduction, though it does not explicitly discuss when not to use it or name alternatives.

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