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

Annotations already declare non-destructive, idempotent, and non-read-only. The description adds the requirement to include a conversation array for reproduction, which is extra context beyond annotations. However, it does not disclose what happens after reporting (e.g., confirmation, ID returned), so it adds limited transparency.

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?

Two concise sentences, front-loaded with the core purpose and a practical hint about the conversation. No redundant information or fluff; every word serves a purpose.

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 reporting tool with no output schema, the description covers the purpose and a key input but omits details about outcomes or return values. Given the low complexity and available annotations, it is adequate but not fully complete—more could be said about expected behavior after submission.

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 has zero description coverage, so the description must compensate. It explains the conversation parameter's purpose (for reproduction) but leaves 'message' and 'context' without explicit explanation. It adds some value but does not fully clarify all parameters, earning a middle score.

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 explicitly states the tool reports bugs, missing features, or feedback, with a clear verb and resource. It distinguishes from siblings like authenticate or connect by focusing on issue reporting, and even hints at a key input (conversation) for reproduction.

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 purpose clearly implies when to use (when a user wants to report an issue or send feedback). There are no explicit alternatives or exclusions, but the context is clear and the tool is specialized for this task, making usage unambiguous.

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