number_random

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

Annotations already cover the safety profile (readOnly, non-destructive), so the description should add what's missing – but it says nothing about what is returned (a fact string? a number?), whether results vary per call, or what the openWorldHint source is. Note the idempotentHint=true sits awkwardly with a tool advertised as 'random', and the description does nothing to clarify that tension.

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 short sentence with no filler, so it is structurally clean, but it is terse to the point of under-specification rather than genuinely concise.

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 three undocumented parameters, no output schema, and no explanation of the return shape or the meaning of 'type', the definition leaves too much unresolved for correct invocation. A one-clause description cannot carry a 3-param tool with zero schema coverage.

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% and three parameters (min, max, type) are completely undocumented in both places. The phrase 'random number fact' faintly hints that min/max bound the number and type selects the fact category, but it never says so, so the agent must guess at accepted 'type' values.

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 reads as a compound noun phrase ('random number fact') that could mean either 'generate a random number' or 'return a fact about a random number' – the two readings imply very different behavior. It also fails to distinguish itself from the sibling number_fact (and random_number), which an agent would have to disambiguate by opening schemas.

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 statement of when to use this tool versus number_fact, number_random's near-duplicate, or random_number. No prerequisites, no exclusions, no examples of the 'type' concept that would let an agent judge appropriateness.

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