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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false. The description adds real behavior beyond that: submissions stay private, operator review is required, votes cannot promote a code to public/verified, and the server does not fetch user URLs. It never explains the idempotency contract implied by request_key, which is the most operationally important trait for a retryable write.

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?

Front-loaded with the action, followed by prohibitions and privacy guarantees. Sentences are tight, though the votes sentence is somewhat tangential and the trailing whitespace/multi-line formatting is untidy.

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?

An output schema exists, so return values need not be described. For a 4-required-param write with zero schema coverage, the missing request_key and provider semantics leave a real gap an agent could get wrong.

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 carry the burden. It clarifies source_url ('URLs are evidence; the server does not fetch user URLs') and implies code must be public rather than secret, but 'provider' and especially 'request_key' (8-128 chars, presumably an idempotency key) get no explanation at all.

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?

States a specific verb and resource: submit a publicly shareable promo code plus its source for operator review. The scope ('publicly shareable', 'for operator review') separates it from claim_offer and request_promotion without naming a sibling outright.

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?

Gives explicit when-not guidance: never submit API keys, account-specific vouchers, or secrets. It also pre-empts a misuse case (submitting to gain votes/verification). It does not name an alternative tool for the excluded cases (e.g. request_promotion), so it stops short of full routing.

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