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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld false), so the bar is lower, and the description still adds a real behavioral guarantee: 'every order is equally likely' (uniform permutation). The 1000-item ceiling is also surfaced. It omits that repeated calls with the same items produce different results unless seeded, which is only implied via idempotentHint=false.

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?

A single clause pair with zero filler, and the key constraint (1000 items) and the core guarantee are both front-loaded.

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, side-effect-free permutation tool with annotations covering safety and the schema covering the seed, the description is nearly sufficient. The only minor gap is that it never says the shuffled list is what gets returned, which the absent output schema would otherwise need to clarify.

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 50%: the seed parameter is well documented in the schema (64 hex chars, replay semantics), while items has no schema description. The description corroborates the item limit ('up to 1000 items') but adds nothing about the seed beyond what the schema already states, so the baseline 3 applies.

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 (put in a random order) and the resource (a list of items), so an agent immediately understands this permutes the whole input rather than selecting a single element. It doesn't explicitly name sibling pick_from_list, which is the closest adjacent operation, so it stops short of full differentiation.

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 is implied by the operation itself—shuffle the list rather than pick one item or roll dice—but there is no explicit when-to-use or when-not-to-use statement, and no mention of the seed-replay scenario for verification. The schema's seed description carries that usage context instead.

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