random

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

The description discloses that the number is 'pseudo-random' and the range, but it does not explain whether the maximum is inclusive/exclusive, what happens if no maximum is specified, or the type of number (integer/float). Since no annotations are provided, the description fails to fully describe behavior.

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?

The description is a single sentence, front-loaded with the core action and scope. It contains no filler and effectively conveys the main purpose and a key constraint in minimal space.

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?

Given the lack of annotations and output schema, the description must explain return behavior and invocation. It fails to specify how the maximum is passed, the inclusivity of the range, or the output type, making it incomplete for an agent trying to use the tool correctly.

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?

The schema has zero parameters, so baseline is 4, but the description refers to a 'specified maximum' without explaining how it is provided. This creates confusion and actively contradicts the schema, reducing the clarity of the tool's interface.

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 ('Generates') and resource ('pseudo-random number'), and specifies the range from 0 to a maximum. It is clear what the tool does, though the reference to a 'specified maximum' is confusing given that the schema has no parameters.

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?

No guidance is provided on when to use this tool versus alternatives. The only contextual information is the constraint on valid maximum values, but there is no mention of use cases or exclusions.

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