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

Annotations already cover safety and idempotency: readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds the useful expectation that recent conversation content should be included for reproduction, though it does not disclose side effects after submission, consent, auth, or rate limits.

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 tight sentences with no padding: use cases are named first and the repro guidance is given second. It is well-structured for easy scanning.

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 feed-back tool, the description captures the main purpose and a key usage nuance, but it leaves required-parameter guidance, conversation serialization format, and expected feedback side effects/messages under-specified. It is minimally viable but not complete.

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 should carry most parameter meaning. It only covers the optional 'conversation' field, and 'array' conflicts slightly with schema's string type. The required 'message' parameter and the optional 'context' parameter receive no meaningful explanation.

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 explicitly states the tool's concrete purposes: fix it, missing feature, and feedback — using 'Report', a specific verb. This clearly distinguishes it from sibling tools like authenticate or marketplace.

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 clearly says when to use it: for bug reports, missing features, or feedback, and gives an explicit instruction to include the conversation for reproduction. It does not mention when not to use it or name alternative tools, so it stops short of fully explicit exclusion guidance.

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