next_prime

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

No annotations are provided, so the description carries full burden. It states the tool's function but lacks behavioral details such as performance characteristics (e.g., computational limits for large inputs), error handling for invalid inputs (e.g., negative numbers), or output format. This is a significant gap for a tool with no annotation coverage.

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, efficient sentence that front-loads the core purpose, followed by domain/category tags. There is no wasted verbiage, making it highly concise and well-structured for quick understanding.

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 tool's low complexity (one integer parameter) and no output schema, the description is minimally adequate but incomplete. It lacks details on output (e.g., returns an integer prime), error cases, or performance limits, which are important for an agent to use it correctly without annotations.

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 description adds meaning by specifying that the input 'n' is the number to start from ('greater than the given number'), which clarifies the parameter's role beyond the schema's basic integer type. With 0% schema description coverage and only one parameter, this adequately compensates, though it doesn't detail constraints like non-negative integers.

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 clearly states the specific action ('Find the next prime number') and the resource ('greater than the given number'), with domain/category context. It distinguishes from siblings like 'is_prime', 'nth_prime', or 'first_n_primes' by focusing on the next prime after a given input.

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 explicit guidance on when to use this tool versus alternatives (e.g., 'is_prime' for primality testing, 'nth_prime' for a specific prime index, or 'prime_count' for counting primes). The description implies usage for finding the next prime but lacks comparative context with sibling tools.

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