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

Annotations already disclose readOnlyHint=false, destructiveHint=false, and idempotentHint=true, which establish the behavioral profile. The description adds the note that conversation should include recent messages for reproduction, which is helpful context but does not describe side effects, return values, or failure modes. This is consistent with the annotation-provided baseline.

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, front-loaded with the tool's purpose, and contains no redundant or filler words. Every sentence earns its place by providing distinct information.

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?

With no output schema and no parameter descriptions, the description covers the core purpose and gives a key usage tip, but it omits what happens after reporting, how to use 'context', and any behavioral side effects. Given the tool's simplicity, this is adequate but leaves noticeable gaps.

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 clarifies the 'conversation' parameter by instructing to include recent messages for reproduction, but it does not describe the required 'message' parameter or the optional 'context' parameter. This leaves significant ambiguity for the agent, especially for 'context'.

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 clearly identifies the resources: 'a bug, missing feature, or send feedback.' It is unambiguous and easily distinguishes this tool from the unrelated sibling tools.

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 states explicit usage scenarios (bug, missing feature, feedback) and provides a practical instruction to include the conversation array for reproduction. It does not mention exclusions or alternatives, but no closely related siblings exist, so the guidance is sufficient.

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