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

Annotations already indicate non-read-only, idempotent, non-destructive behavior. The description adds no further behavioral context—no mention of side effects, output, auth requirements, or any limits. It only restates the purpose and gives a parameter hint, which is insufficient for a tool that presumably sends data somewhere.

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 a single sentence that conveys purpose and a key usage instruction with no filler. It is front-loaded and every word earns its place.

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 one required parameter and annotations, the description covers basic selection and invocation. However, it lacks important context such as when to use it vs. other reporting mechanisms, what happens after submission, and clarification of the remaining parameters. It is minimally viable but not comprehensive.

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 partially explains the 'conversation' parameter ('array with recent messages for reproduction'), but the required 'message' parameter is not explicitly described, and 'context' is entirely undocumented. The description is too vague to fully guide correct invocation.

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: 'Report a bug, missing feature, or send feedback.' This is a specific verb plus resource, and it distinguishes the tool from its unrelated siblings (authenticate, connect, etc.). It leaves no ambiguity about what the tool does.

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 instruction to 'Include the conversation array with recent messages for reproduction' gives a concrete usage hint, and the tool's purpose is evident given unrelated siblings. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites.

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