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

Annotations already cover read-only, destructive, and idempotency traits, lowering the burden on the description. The description adds useful context by requiring the conversation array for reproduction, but it does not clarify side effects, submission behavior, or whether a report creates a ticket or notification.

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?

Two concise sentences deliver the main purpose and the most important usage detail without fluff. The description is front-loaded and every word adds value.

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 3-parameter tool with no output schema, the description covers the core purpose and the key reproduction requirement. However, the ambiguity around the conversation parameter's type (array vs. string) and the undocumented context parameter leave minor gaps that could affect correct invocation.

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 explains that conversation should contain recent messages for reproduction, and message is implied as the report content. However, it does not explain the context parameter, and the phrase 'conversation array' conflicts mildly with the schema's string type (likely JSON-encoded).

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 clearly states a specific action ('Report') and concrete targets ('a bug, missing feature, or send feedback'). It is immediately distinguishable from sibling tools like authenticate or show_version, which have completely different purposes.

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 communicates straightforwardly when this tool is appropriate: whenever a user wants to report a bug, missing feature, or give feedback. It also gives a practical prerequisite—including the conversation for reproduction—though it does not explicitly address exclusions or alternatives, which are not critical given the unrelated sibling tools.

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