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

The description does not disclose what happens after reporting (e.g., ticket creation, email notification) or any side effects. The annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds no context about the actual behavior beyond the action itself.

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 concise, consisting of two sentences that cover the purpose and a key usage instruction. It is well-structured and free of unnecessary detail.

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 the core purpose and a hint about parameter usage, but omits details about expected output, error handling, or post-action effects. Given the simple nature of the tool and the presence of annotations, it is minimally complete but lacks depth.

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?

The description clarifies the purpose of the 'conversation' parameter (for reproduction), but leaves 'message' and 'context' undefined. Since the schema provides no descriptions for these fields, the description only partially compensates for the lack of parameter documentation.

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: reporting bugs, missing features, or feedback. The verb 'report' and resource specification make the action unambiguous, and it is distinct from the sibling tools listed.

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 a specific instruction to include the conversation array for reproduction, which is a direct usage guideline. It implicitly indicates when to use this tool (when reporting issues), though it does not explicitly exclude alternative tools. Given no obvious alternatives exist, this is acceptable.

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