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

Annotations indicate idempotentHint=true and destructiveHint=false, but no readOnly hint. Description adds no extra behavioral details (e.g., no mention of the side effect of reporting, rate limits, or whether it creates a ticket). The description adds minimal beyond annotations, but without contradicting them, so a 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?

Two concise sentences, front-loaded with the purpose and a key instruction. No fluff, every word earns its place.

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?

The tool is simple (3 params, no output schema), but the description only partially covers parametersais specifically conversation. Missing details about 'context' and the exact format for 'message' or how they are used. For a low-complexity tool, it is adequate but not fully complete.

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 coverage is 0% and description only mentions 'conversation' for reproduction. It does not explain the 'context' parameter or clarify 'message' beyond being the report text. It adds some value for conversation but leaves most parameters unexplained, so it falls short of the baseline for compensating low coverage.

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?

Clear and specific: 'Report a bug, missing feature, or send feedback.' Distinct from sibling tools (show_version, authenticate, etc.), with an explicit resource and action.

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?

Tells when to use (bug/feature/feedback) and gives a practical tip ('include conversation array for reproduction'). Does not explicitly mention alternatives, but none are needed given the sibling set. Lacks explicit 'when not to use' but still provides clear context.

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