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

The description does not contradict annotations (idempotent, non-destructive, non-read-only). It adds the requirement to include conversation for reproduction, but does not disclose what happens upon calling (e.g., creates a ticket, sends an email) or mention idempotency, which is already covered by the idempotentHint annotation.

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 instruction. No filler or redundant 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?

For a simple tool with only 3 parameters and no output schema, the description is adequate but incomplete: it covers the main purpose and flags the key parameter (conversation), but does not define 'message' or 'context', nor describe expected outcomes or error cases. This is acceptable but not comprehensive.

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 description coverage is 0%, so the description must compensate. It explains the 'conversation' parameter (include array with recent messages for reproduction) but does not clarify 'message' or 'context'. This is partial compensation; without describing all parameters, it leaves some ambiguity.

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?

Purpose is clear: 'Report a bug, missing feature, or send feedback' uses a specific verb (report) and resource (bug/feature/feedback). This clearly distinguishes itself from sibling tools like authenticate and show_version, which serve unrelated 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?

Provides context by instructing to include the conversation array with recent messages for reproduction, implying when to use (when reporting bugs/feedback). However, it does not explicitly mention exclusions or alternatives, but given sibling tools are unrelated, this is acceptable.

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