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

Annotations already indicate the operation is non-destructive and idempotent, and the description does not contradict these. The description adds the useful behavioral note about including recent messages for reproduction but does not explain side effects, whether a response is returned, or how the report is handled.

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 concise sentences with no filler. The first sentence states the purpose, and the second provides an actionable usage note, so every word earns its place.

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, the description covers the main inputs and reproduction guidance. It is slightly incomplete because `context` is unexplained and no output behavior is mentioned, but the absence of an output schema and nested objects lowers the need for deeper detail.

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 needs to carry parameter meaning. It partially does, clarifying that `conversation` is an array of recent messages and `message` is the report text. However, the `context` parameter is never explained, leaving one of three params ambiguous.

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 with a specific verb ('Report') and identifies the three kinds of content it handles: bugs, missing features, and feedback. It is distinct from sibling tools like authenticate or marketplace, so an agent can easily select it for 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?

The text provides actionable context for when to use the tool and even specifies that the conversation array should be included for reproduction. There is no explicit when-not-to-use guidance, but no other sibling tool appears to serve a similar reporting or feedback purpose.

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