List Number Ranges

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

No annotations are available, so the description must fully disclose behavioral traits. It only states the action 'list', which implies read-only, but it does not confirm safety, mention pagination, rate limits, or any side effects. The lack of detail leaves the agent with minimal behavioral context.

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 concise sentence with no unnecessary words. It is front-loaded with the action and resource, making it efficient and easy to parse.

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 no output schema, the description should at least hint at what is returned (e.g., fields, format, or count). It only says 'number range objects', which is vague. For a tool with zero parameters, the description could elaborate on the scope of the 'configured' ranges or expected output structure.

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 tool has zero parameters, so the description cannot add parameter meaning beyond the schema. According to guidelines, 0 parameters sets a baseline of 4. The description does not introduce any confusion or misleading information about inputs.

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 action ('List') and the resource ('configured number range objects'). It directly mirrors the name and title, but it is specific enough to indicate what the tool does. Despite being short, it is unambiguous and distinct from sibling tools like 'create_number_range'.

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 usage guidelines are provided. The description does not specify when to use this tool versus any alternatives. Even if the tool is straightforward, explicit guidance on when-not-to-use or prerequisites is missing, which is a gap for an AI agent evaluating multiple similar tools.

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