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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds minimal behavioral context beyond that, only instructing to include the conversation array for reproduction. It doesn't describe side effects (e.g., sending data) or response behavior, but since annotations cover the safety profile, 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 very concise—two sentences—and front-loads the core purpose. Every sentence adds value: the first states what the tool does, and the second provides a key usage hint. No wasted words.

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?

With only 3 simple parameters and no output schema, the tool is relatively straightforward. The description adequately explains the tool's purpose and provides guidance on one important parameter. However, it does not clarify the 'context' parameter or what happens after reporting (e.g., confirmation), but these are minor gaps for a tool of this simplicity.

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 partially explains the 'conversation' parameter (for reproduction) but says nothing about 'message' or 'context'. The main parameter 'message' is inferred from the tool name, but 'context' remains ambiguous. Given the low coverage, the description falls short.

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.' This is a specific verb ('report') combined with a resource (bug/feature/feedback), and it is clearly distinct from siblings like authenticate or show_version, which serve different functions.

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 gives clear context: use when you want to report an issue or feedback. It also provides a specific usage hint: 'Include the conversation array with recent messages for reproduction.' However, it does not explicitly mention when not to use this tool or alternatives, so it falls slightly short of the highest tier.

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