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

Annotations already indicate non-read-only but non-destructive behavior. The description adds useful context by instructing users to include conversation data for reproduction, which is behavioral guidance beyond the annotations. While it doesn't mention rate limits or auth, the simple nature of this tool and the presence of annotations lower the bar, and the description adds value.

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 a single, concise sentence that front-loads the purpose and includes a direct instruction in the second part. Every word earns its place; no fluff or redundancy. This is a model of efficient writing.

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 no output schema, three flat parameters, and one required field, the description is mostly sufficient. It explains the key invocation detail (include conversation array). It loses a point for not clarifying what the 'message' parameter is for, especially since it's the only required parameter, but overall the tool is simple enough that this is a minor gap.

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?

With 0% schema description coverage, the description must compensate by explaining parameters. It only addresses the 'conversation' parameter explicitly, leaving 'message' and 'context' unexplained. Since it covers only one of three parameters and adds no details on format or required fields, it falls short of the need. A score of 2 reflects the partial but insufficient compensation.

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 resource ('a bug, missing feature, or send feedback'). It also provides an important scoping detail (include conversation array) that distinguishes it from sibling tools like 'show_version' or 'authenticate'. This is exactly what a purpose statement should do.

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 makes it clear when to use the tool (when reporting a bug, missing feature, or feedback) and even gives a concrete instruction on what to include (conversation array). However, it does not explicitly name alternatives or exclusions, though siblings are unrelated. It slightly misses the 'alternatives named' bar, so a 4 is appropriate.

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