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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description doesn't need to cover safety. It adds useful behavioral context by instructing to include the conversation array for reproduction, which helps the agent prepare a meaningful report.

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?

A single sentence that is direct and front-loaded. It could benefit from more detail, but current structure is efficient and not wasteful.

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 description provides basic intent but omits what happens after reporting (e.g., confirmation, ticket ID), doesn't clarify the conversation string format, and gives no guidance on the required message field. This leaves room for misunderstanding in practical use.

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 only explains the conversation parameter's purpose, leaving the required 'message' and optional 'context' unexplained. Additionally, it calls conversation an 'array' while the schema types it as a string, creating ambiguity.

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 function: reporting bugs, missing features, or sending feedback. This verb+resource phrasing distinguishes it from the unrelated siblings like authenticate 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?

It gives clear context for when to use (when reporting issues or feedback) but doesn't explicitly mention when not to use or name alternatives. Since none of the sibling tools are similar, the intended usage is clear without exclusions.

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