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

Annotations already indicate readOnlyHint=false and destructiveHint=false, but the description adds little beyond that. It does not disclose what happens after reporting (e.g., ticket creation, asynchronous submission) or any side effects. The only extra context is reproduction guidance, which is parameter-focused.

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 sentences communicate the full purpose and essential guidance. There is no filler or redundancy, though the 'conversation array' phrasing could be tightened to match the schema's string type.

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 low-complexity reporting tool with one required parameter and no output schema, the description covers the core purpose and reproduction information. However, it omits what response to expect, how `context` is used, and misstates the type of `conversation`, leaving notable gaps.

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 explains the `conversation` parameter ('recent messages for reproduction') but incorrectly calls it an array when the schema declares a string. It leaves `context` completely unexplained and `message` is only implied by the main verb.

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') and names distinct resource types: bug, missing feature, or feedback. This clearly differentiates the tool from sibling tools like authenticate or 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?

It states when to use the tool ('Report a bug, missing feature, or send feedback') and provides reproduction guidance ('Include the conversation array with recent messages'). It does not explicitly name alternatives or exclusions, but the context is clear.

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