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

The description discloses expected behavior by instructing to include the conversation array for reproduction. It does not contradict the annotations (idempotent, non-destructive) and provides transparency about input requirements beyond what the schema offers.

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, one sentence, and efficiently conveys the purpose and a key instruction. It is well-structured and free of fluff.

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 is sufficient for a simple reporting tool. It explains what to do and what to include, and there is no output schema to worry about. Minor gap: it does not mention any return value or confirmation, but that is not critical for this action.

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 schema has no descriptions for parameters. The description only mentions the conversation array, but does not explain the required 'message' parameter or the optional 'context' parameter. With 0% schema coverage, the description fails to compensate for most parameters, leaving 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 feedback. It is specific and distinct from sibling tools like authentication or version info.

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 implies the intended use case (reporting issues) and provides a specific instruction to include the conversation array, which is a guideline. It does not explicitly contrast with alternatives, but the context makes it obvious.

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