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

Annotations already indicate idempotentHint=true and destructiveHint=false, and the description does not contradict them. It adds a small amount of behavioral context by asking for the conversation array for reproduction, but it does not disclose what happens after reporting or any side effects.

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 short, front-loaded sentences describe the purpose and include the key usage hint. Every sentence earns its place, with no redundant or vague filler.

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 report tool with 3 parameters and no output schema, this is near minimal viable. The description provides enough to understand the core intent, but the lack of parameter-level detail and the string-vs-array ambiguity leave gaps for an agent to guess formats.

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 the burden. It only explains the conversation parameter, and calls it an 'array' while the schema types it as string with default '[]'. The 'message' parameter is implied by tool name, and the 'context' parameter is not mentioned at all.

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 starts with 'Report a bug, missing feature, or send feedback,' giving a specific verb and resource. It distinguishes this tool from the sibling tools, none of which are about reporting or feedback.

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 states when to use the tool: when a bug, missing feature, or feedback arises. It does not explicitly call out alternatives or exclusions, but no sibling tool offers this functionality, so the context is sufficient.

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