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

The annotations already indicate the operation is idempotent, non-read-only, and non-destructive. The description adds useful context that recent conversation messages should be included for reproduction, but it does not disclose the processing side effects or what happens after the report is sent.

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 focused sentences, front-loaded with the tool's purpose. Every sentence earns its place, and there is no vague filler.

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, this is a mostly sufficient level of detail given the annotations and simple schema. However, the required message field and optional context field are not meaningfully explained, and the absence of an output schema means the response format is never mentioned.

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 carries the burden for explaining parameters. It only clarifies the conversation parameter (recent messages for reproduction); the required message parameter and context parameter are left undocumented, and the description's 'conversation array' wording does not match the schema's string type.

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 uses a specific verb ('Report') and clear resource targets ('bug, missing feature, feedback'), making the tool's purpose immediately obvious. It is clearly distinct from sibling tools like authenticate, connect, and marketplace.

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 explicitly states when to use the tool: for bugs, missing features, or feedback. It also instructs the agent to include the conversation array for reproduction, but it does not mention when not to use the tool or name alternative tools.

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