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

Annotations only declare safety flags; the description goes well beyond them by disclosing the algorithm (Fisher-Yates with a cryptographic random source, implying unbiased, non-reproducible output), the payment model ($0.001 USDC on Base), the payment protocol (x402), and that charging happens only per successful call. This is exactly the kind of cost, auth, and determinism 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?

Three dense sentences, each earning its place: what it does, when to use it, what it costs. The purpose is front-loaded and no sentence is filler.

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?

Covers input format, use cases, algorithm, and the unusual payment requirement, which is the highest-risk unknown for an agent. The one gap is the return shape (presumably the shuffled list as a string) and how the x402 payment is actually presented, but with no output schema and simple input, this is close to 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?

Single parameter with 100% schema description coverage, so the schema already documents 'items' as comma-separated. The description adds newline-separated support not present in the schema, which is genuinely useful, but it gives no guidance on delimiters in item content or empty/whitespace handling. Baseline 3 is appropriate given the schema does most of the work.

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 (shuffle) and resource (comma- or line-separated list) plus the exact algorithm and randomness source, so an agent knows precisely what it does. It does not name or contrast any sibling (e.g. random_pick or random_teams), leaving the agent to infer the distinction from the verb alone.

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?

'Use for draw orders, seating and playlists' gives concrete when-to-use contexts rather than leaving usage implied. There is no guidance on when NOT to use it (e.g. when you want a single pick or a deterministic ordering), so it falls short of explicit alternatives.

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