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

Annotations already declare readOnlyHint false and idempotentHint true, indicating it is a mutating but idempotent call. The description adds only a hint about including conversation data for reproduction, but does not disclose side effects, required permissions, or any limitations beyond what annotations convey. No contradiction with annotations, but minimal additional behavioral context.

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: the first states purpose, the second gives a specific usage hint. Every word earns its place, no redundancy, and it is 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?

The tool has 3 parameters and no output schema. The description covers purpose and one parameter (conversation), but leaves 'context' and return behavior unexplained. Given the low schema coverage, more detail would be helpful, but the tool is simple and the description is adequate for a basic reporting 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?

With 0% schema description coverage, the tool description must explain all parameters. It explains 'conversation' (the array with recent messages) and implicitly suggests 'message' holds the bug content, but leaves 'context' undefined. The description adds some meaning but does not compensate fully for the missing schema documentation.

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: 'Report a bug, missing feature, or send feedback.' This is a specific verb (report) with clear resource categories, and it distinguishes from sibling tools like authenticate or connect that serve different functions.

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 when to use the tool by defining its purpose, and adds a concrete instruction: 'Include the conversation array with recent messages for reproduction.' However, it does not explicitly mention alternative tools or scenarios where this tool should not be used, but siblings are unrelated, so the context is sufficient.

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