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

Annotations already reveal non-read-only, idempotent, non-destructive behavior. The description adds the useful detail that the conversation array should be included for reproduction, but it doesn't disclose other behavioral aspects such as whether a confirmation is returned or how the report is processed. This is moderate added value beyond 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?

The description is two sentences long, front-loads the purpose, and ends with a specific, necessary instruction about the conversation array. There is no extraneous text, making it both concise and effectively structured.

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 three string parameters and no output schema, the description is mostly adequate. However, it omits the 'context' parameter entirely, doesn't mention any response or post-submission behavior, and leans on annotations for safety. This is a moderate gap given zero schema coverage.

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 descriptions cover 0% of parameters, so the description must compensate. It only explains the 'conversation' parameter ('Include the conversation array with recent messages'), leaving 'context' completely unexplained and 'message' only implicitly the report text. No format details are given for the conversation JSON string, and the 'context' parameter is a significant gap.

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 reports a bug, missing feature, or sends feedback, using an explicit verb ('report') and three distinct resource types. This distinguishes it from sibling tools like authenticate or connect, which serve different purposes.

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 this tool (when the user reports a bug or provides feedback) and gives specific guidance to include the conversation array for reproduction. It doesn't explicitly say when not to use it, but the context is clear and no alternative reporting tool exists among siblings.

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