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

Annotations already establish non-read-only, idempotent, and non-destructive behavior. The description adds context about including the conversation array for reproduction, which is a behavioral nuance. It does not disclose side effects like where the bug report goes, but with annotations covering safety, this is adequate.

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 only two sentences, front-loaded with the purpose and then a key usage note. Every word contributes to understanding, with no filler or redundancy.

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 bug-report tool with no output schema, the description covers the core action and highlights the most important parameter. It lacks any mention of return values or post-call behavior, but given the tool's low complexity, this is a minor gap. Overall, it is sufficient for an agent to invoke correctly.

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 coverage is 0%, so the description must compensate. It explains the 'conversation' parameter's purpose ('recent messages for reproduction') but does not clarify 'context' or 'message' beyond what their names imply. This gives partial parameter guidance but not full coverage of all three parameters.

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 'Report a bug, missing feature, or send feedback,' providing a specific verb and resource that distinguishes it from sibling tools like authenticate and connect. The purpose is unambiguous and immediately understandable.

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 indicates when to use the tool ('Report a bug, missing feature, or send feedback') and provides a concrete instruction ('Include the conversation array with recent messages for reproduction'). However, it does not explicitly mention alternatives or exclusions, though siblings are unrelated so no conflict is expected.

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