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

Annotations are present (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the bar is lower. The description adds context about requiring the conversation array for reproduction, which is useful behavioral insight beyond the annotations. No contradiction.

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, front-loaded with the main purpose, 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堪3 params, one required, no output schema—the description is adequate but not fully complete. It explains the conversation parameter's purpose, but 'context' remains unexplainedholistically. For a simple tool, it's sufficient but not exemplary.

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 coverage is 0%, so description must carry the weight. It explains the conversation parameter's purpose but doesn't explain 'context' or 'message' beyond obvious. The description partially compensates but not fully—message is clear, context is vague, and conversation is explained.

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 purpose: report a bug, missing feature, or send feedback. It uses a strong verb ('report') and identifies the resource (bug/feature/feedback), which distinguishes it from sibling tools 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 gives concrete guidance on when to use (report issues) and how to use (include conversation array). It doesn't explicitly mention alternatives or when not to use, but the purpose is clear enough. Since siblings are unrelated (authentication, version info), no conflict arises.

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