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

Annotations already convey the safety profile (not read-only, not destructive, idempotent). The description adds useful guidance by instructing to include the conversation array for reproduction, which implies the report will be used for debugging. However, it does not disclose what happens after submission (e.g., where the report goes, expected response), and it does not explain the idempotent hint, so some behavioral ambiguity remains.

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 a single, front-loaded sentence that states the purpose and immediately gives the key usage instruction. Every word earns its place, and there is no wasted verbiage.

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 is simple with three string parameters and no output schema. The description covers the purpose and one parameter (conversation) but omits details about the 'message' and 'context' parameters, and it misrepresents the conversation field as an array rather than a JSON string. This is adequate but not fully complete for an agent to invoke it correctly without additional assumptions.

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 by explaining parameters. It explicitly mentions 'conversation array' and indirectly alludes to 'message' via 'send feedback,' but the 'context' parameter is entirely unexplained. Moreover, it calls 'conversation' an array while the schema expects a string, which could mislead users. This leaves significant gaps in parameter understanding.

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.' The verb 'report' and direct listing of report types distinguish it from sibling tools like authenticate or show_version, making its role immediately understood.

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: any time the user needs to submit a bug report, feature request, or general feedback. It does not explicitly mention alternatives or exclusions, but the context is unambiguous and no other sibling tool serves the feedback purpose.

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