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

Annotations declare idempotentHint=true and destructiveHint=false, indicating a safe, idempotent operation. The description adds that it expects a conversation array for reproduction, which is useful behavioral context. No contradiction. However, it doesn't disclose what happens after submission (e.g., acknowledgment, no side effects), though annotations cover safety.

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 sentences, concise and front-loaded. The first sentence states the purpose, the second adds a key usage detail. No fluff.

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 tool's simplicity and lack of output schema, the description covers the basic purpose but omits critical parameter details. With 3 params and zero schema coverage, the description should explain each parameter's meaning at least briefly. It also doesn't mention whether any authentication is required, though siblings include authenticate. Overall, it's minimally adequate but with notable 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?

The schema has 3 parameters with 0% description coverage. The description only mentions 'conversation array' among the three, leaving 'message' and 'context' undocumented. It doesn't clarify the format of 'conversation' (string containing JSON array) or the purpose of 'context'. With 0% coverage, the description must compensate but only partially does.

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 the tool's purpose: 'Report a bug, missing feature, or send feedback.' It names the action (report) and the target (bug, missing feature, feedback), which is specific enough. It doesn't explicitly differentiate from siblings, but siblings are unrelated (authenticate, show_version, etc.), so no ambiguity.

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?

It implies when to use it (when you identify a bug or missing feature or want to give feedback), but doesn't explicitly state when not to use it or alternatives. Given the sibling tools are unrelated, this is acceptable but could be stronger with a direct 'Use when...' statement.

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