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

Annotations already convey read-only, destructive-Hint, and idempotence. The description adds one behavioral detail: the conversation data is needed for reproduction. It does not disclose what happens after submitting, such as whether a ticket is created or if data is sent externally, leaving some side-effect details unexplored.

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 exactly two sentences: the first states the purpose, the second gives necessary reproduction guidance. Every sentence contributes value, and the most important information is front-loaded.

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?

Given three parameters and no output schema, the description is thin. It does not explain what the agent or user will receive after a successful report, how to structure the optional `context` parameter, or how the conversation should be serialized. The purpose is clear, but the full operational picture is incomplete.

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?

With 0% schema coverage, the description must carry parameter meaning. However, it refers to a 'conversation array' while the schema types conversation as a string (defaulting to '[]'), which is misleading for an agent. The `message` and `context` parameters are not clarified beyond the tool's broad purpose.

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 opens with a clear verb-resource pairing: 'Report a bug, missing feature, or send feedback.' This captures the purpose explicitly and distinguishes the tool from all six siblings, none of which relate to bug reporting or feedback.

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 first sentence directly states when to use the tool (for bugs, missing features, or general feedback), and the second sentence provides actionable guidance about including the conversation for reproduction. It lacks explicit exclusions or alternatives, but the unrelated sibling set makes those less necessary.

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