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

The description adds behavioral context beyond annotations by mentioning the inclusion of conversation messages for reproduction. Annotations declare idempotentHint=true and destructiveHint=false, which the description implicitly supports.

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 two sentences with no unnecessary content. It is front-loaded with the action and provides key advice about the conversation array.

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 reporting tool with 1 required parameter and no output schema, the description covers the basic action and includes a suggestion for reproduction. However, it does not mention what happens after reporting (e.g., ticket creation, no return value).

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 explain parameters. It only hints at the 'conversation' parameter but does not detail 'message' (required) or 'context'. This leaves agents unclear about parameter usage.

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 reports bugs, missing features, or sends feedback, providing a specific verb and resource. While it doesn't explicitly differentiate from siblings, the sibling tools are distinct (e.g., wise_*, authenticate, marketplace).

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 advises including the conversation array for reproduction, but lacks explicit when/why to use this tool over alternatives. However, no sibling tool serves a similar purpose, making usage somewhat intuitive.

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