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

The annotations do not include readOnlyHint or destructiveHint, but the description itself indicates the message is transmitted as a report, which is a write-like action. It also instructs the caller to include a 'conversation array' for reproduction, adding behavioral context. However, it does not disclose the response format, whether a report ID is returned, or any side effects such as user notification, so transparency is partial.

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 entire description is only two sentences: the first states the core purpose, the second gives the one critical usage tip. There is no filler, no redundant schema repetition, and the structure is easily digestible.

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 tool with a single required parameter and no nested objects, the description provides enough context to formulate a bug report and indicates what to include for reproduction. The absence of output schema makes return value description less important, though a brief note about what the user should expect after submission would have made it fully complete.

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?

The schema description coverage is 0%, so the description must clarify parameters. It does explain that 'conversation' should contain recent messages for reproduction, adding meaning to an otherwise opaque string parameter. However, the description calls it an 'array' when the schema defines it as a string, and it does not mention the optional 'context' parameter at all, leaving semantic gaps.

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 opens with the specific verb 'Report' and specifies the resource types: 'a bug, missing feature, or send feedback.' This directly states what the tool does and clearly distinguishes it from sibling tools like 'marketplace' or 'show_version', which serve entirely different purposes. It is unambiguous and actionable.

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 gives clear intended context: use the tool to submit a bug report, feature request, or general feedback. The additional instruction to include the conversation array for reproduction tells the user what information to include. It does not mention alternate tools or explicit when-not scenarios, but none of the sibling tools overlap with this report/feedback function, 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.