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

While annotations (readOnlyHint: false, destructiveHint: false, idempotentHint: true) already inform about side effects, the description adds useful context about the `conversation` parameter for reproduction. However, it doesn't elaborate on any other behavioral aspects like rate limits or authentication requirements.

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 extremely concise—two sentences—and front-loads the core purpose. No fluff or repetition; 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?

Given the low complexity (3 flat parameters, no output schema), the description is adequate but could be more complete. It doesn't mention what happens after reporting (e.g., response format, error handling) or clarify that 'conversation' must be a JSON-encoded string, which the schema implies by default. Still, it covers the primary use case sufficiently for a tool of this simplicity.

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. It adds meaning to the 'conversation' parameter by explaining its purpose for reproduction. Yet it leaves 'message' and 'context' undocumented, failing to fully compensate for the lack of schema descriptions.

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 its purpose: 'Report a bug, missing feature, or send feedback.' This is a specific verb+resource and differentiates it from sibling tools like 'show_version' or 'connect', which have 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 implies when to use it (to report issues/feedback) but provides no explicit exclusions or comparisons to alternatives. 'Include the conversation array' offers a hint of usage context but doesn't outline scenarios where this tool should be avoided.

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