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

Goes well beyond the annotations: it discloses that there are no outside side effects, that every successful call costs $0.001 via x402 or prepaid credits, that failed calls are never charged, and it explicitly explains why the tool is not marked read-only or idempotent (repeat calls re-charge). This is exactly the kind of context annotations cannot carry.

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?

Purpose and usage are front-loaded in the first two sentences, and the payment paragraph, though long, is load-bearing because it justifies the non-read-only, non-idempotent annotations. Slightly dense but nothing is wasted.

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?

With no output schema, the description covers purpose, usage, cost, and side effects thoroughly, but never states what is returned (e.g., the chosen items and their order) or how a count larger than the list behaves. Those are the remaining gaps for a two-parameter tool.

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%, so baseline is 3, but the description adds real meaning: it clarifies the list may be comma- or line-separated (the schema only says 'Comma-separated items') and restates the no-repeat constraint on selection. The count parameter's negative minimum is left unexplained, which keeps it below a 5.

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 with a key qualifier: 'Pick one or more items at random (without repeats) from a comma- or line-separated list.' The 'without repeats' scope and list input distinguish it from a plain shuffle, but no sibling (random_shuffle, random_teams, dice, coin) is named, so an agent must infer the boundary.

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?

Offers concrete use cases ('raffles, choosing who goes first, or breaking ties fairly'), which implies when it applies, but gives no when-not conditions and never routes the agent away from near-neighbors like random_shuffle or random_teams. Usage is implied rather than delimited.

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