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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description adds real value on top: submission is anonymous (no account required), payload caps at 500 characters, and several content classes are forbidden. It stops short of saying where the feedback lands or what the response looks like, leaving the odd "waitlist kind=agent" routing opaque.

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?

Four short sentences, no filler, and the hard limits (500 max, forbidden content) are front-loaded. The only weak spot is the cryptic opening token string, which costs a beat of comprehension without adding actionable guidance.

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 single-parameter, non-destructive write with no output schema, most of what an agent needs is present. However, with no output schema the description should say what a successful submission returns or confirms, and it does not, so the agent cannot predict the result of the call.

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 100% and the note field is already documented, so the baseline is 3, but the description contributes meaning the schema lacks: the 500-character limit and the prohibition on firmware, secrets, and vouchers. It also emphasizes that ALL feedback belongs in the single note field, guiding how to pack the argument.

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 states a concrete action ("POST ... Put ALL product feedback in note") and the title names the resource, so an agent knows this submits product feedback. The leading "POST waitlist kind=agent" is internal jargon that obscures rather than clarifies, and the siblings (flash_elf, get_job, list_boards) are unrelated, so no differentiation is needed or offered.

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 gives preconditions and exclusions on content (no firmware, no secrets, no voucher) and says "No account required," which frames when the tool can be invoked. It never states the trigger condition positively (e.g., when the user reports a bug or an API problem) and names no alternative channel.

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