random_pick_from_list

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint and openWorldHint, so safety is fully stated elsewhere. The description adds nothing beyond that: it does not say whether sampling is with or without replacement, whether order of the returned items is randomised, or what happens if count exceeds list length.

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?

One short sentence, front-loaded and free of waste. It is arguably too terse rather than padded, but structurally it is efficient.

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 0% schema coverage and no output schema, the description needs to explain count semantics and return shape and does neither. An agent cannot tell from this definition whether it will get one value or an array, or what count's default and limits are.

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% with two parameters (items, count), so the description carries the burden. It only hints at 'item(s)' implying count > 1, but never states that count is optional, its default, whether it must be <= items length, or whether duplicates are permitted.

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 uses a specific verb ('pick random') and resource ('item(s) from a list'), so the operation is unambiguous. It does not distinguish itself from near siblings such as random_shuffle_list (which reorders rather than samples) or random_number/random_uuid, leaving the agent to infer the difference from the name 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?

There is no guidance on when to use this over random_shuffle_list, which is the obvious alternative for list-randomisation needs. No prerequisites, no mention that it is a pure sampling utility with no side effects beyond what annotations declare.

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