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

Annotations already convey readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds reproduction-related context but does not disclose what happens after submission, whether reports are persisted, or any rate limits. No contradiction with annotations exists.

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 two sentences, front-loads the core purpose, and provides a key usage hint without any redundant phrasing. Every sentence earns its place.

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 reporting tool with no output schema, the description covers purpose and one usage hint, but it omits critical parameter semantics for 'message' and 'context', and the conversation format is ambiguous due to the array/string mismatch. It is minimally adequate but has clear gaps.

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 for the three parameters. It only explains the 'conversation' parameter, and even then calls it an 'array' while the schema types it as a string. The required 'message' parameter and the 'context' parameter are left unexplained, making correct invocation underspecified.

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 the specific verb 'Report' and clearly identifies the targets: a bug, missing feature, or feedback. This distinguishes it from unrelated siblings like authenticate, connect, and show_version, and it expands beyond the title 'Report Bug' by covering additional request types.

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 context for when to use the tool—when the user wants to report a bug, missing feature, or provide feedback—and provides a practical instruction to include recent conversation messages for reproduction. It does not explicitly state when not to use it, but the sibling tools are not plausible alternatives, so no exclusion is strictly necessary.

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