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

Annotations already communicate idempotency, non-destructiveness, and non-read-only behavior. The description adds the purpose of the conversation parameter ('for reproduction') but does not disclose side effects, response behavior, or prerequisites. It is consistent with annotations and provides a moderate amount of extra context.

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, compact sentence that front-loads the tool's purpose before giving the key usage instruction. There is no filler, redundancy, or schema repetition.

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 three plain parameters and no output schema, the description is mostly sufficient: it identifies the purpose, the key required input, and why the conversation data matters. Minor gaps are the unexplained context parameter and the precise serialization of the conversation value.

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, and it partially does: it explains the conversation parameter's role for reproduction. The required message parameter is reasonably implied by 'Report a bug...', but the context parameter is never explained, and saying 'conversation array' is slightly ambiguous given the schema defines it as a string (default '[]').

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 names concrete resource types: a bug, missing feature, or feedback. It also adds the reproduction detail about including the conversation array, which makes the tool's scope clear and distinct from unrelated siblings like authenticate or connect.

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 implies when to use the tool—when reporting a bug, missing feature, or feedback—and gives a concrete instruction to include recent messages for reproduction. However, it does not provide explicit when-not-to-use guidance or name alternatives, leaving usage largely implied.

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