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

Annotations already declare idempotentHint=true and destructiveHint=false, covering the tool's safety profile. The description adds little behavioral context beyond the instruction to include a conversation array, which is more about input than behavior.

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, front-loaded with the action and purpose, and contains no unnecessary information. It is concise and well-structured.

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 tool with three parameters and no output schema, the description covers the core purpose and key parameter guidance. However, it does not specify that 'conversation' is a stringified JSON array (given the string type and default '[]'), which could be ambiguous. Slightly under-specified but adequate for straightforward 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?

The description explains the 'conversation' parameter as 'conversation array with recent messages for reproduction', adding meaning not in the schema. However, 'message' and 'context' are not explicitly detailed, though their names are fairly self-explanatory. With 0% schema description coverage, this partial compensation is adequate but not comprehensive.

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 with a specific verb: 'Report a bug, missing feature, or send feedback.' It identifies the resource (bug/feedback) and is distinct from sibling tools, none of which are about reporting issues.

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 provides a clear use case (report a bug/feedback) and gives practical guidance on including the conversation array for reproduction. No alternatives are mentioned, but siblings are unrelated, so exclusions are unnecessary.

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