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

Annotations already indicate non-read-only and non-destructive behavior. The description adds useful context about including the conversation array for reproduction, but it doesn't disclose what happens after submission (e.g., acknowledgment, ticket creation) or any side effects. No contradiction with annotations.

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, each earning its place: the first clearly states the purpose, the second gives a crucial usage instruction. No redundant or vague wording.

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 description is too sparse for a tool with no output schema and undocumented parameters. It leaves gaps around how to format the 'conversation' (string vs array), the role of 'context', and what response or outcome to expect after reporting.

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 description must compensate. It explains the purpose of the 'conversation' parameter but not 'message' or 'context'. Also, it calls it 'conversation array' while the schema expects a string, creating ambiguity about serialization.

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 with a specific verb ('Report') and resources ('a bug, missing feature, or send feedback'). It effectively distinguishes this from sibling tools like 'authenticate' or 'show_version' by focusing on issue reporting.

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?

It provides clear context for using the tool: to report issues or feedback. The instruction to include the conversation array for reproduction implies when it's useful, and there are no competing alternatives among siblings. However, it doesn't explicitly state when not to use it.

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