list_rate_bands

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

The annotations already provide read-only, idempotent, open-world, and non-destructive hints. The description adds no behavioral context beyond the word 'List', such as pagination defaults, ordering, or any filtering semantics, so it provides no value beyond the structured annotations.

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 three words and contains no filler, making it very concise and front-loaded. However, it is so minimal that it relies heavily on the name and schema, though this is not penalized heavily here because conciseness itself is strong.

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?

The tool is simple, has well-documented optional parameters, no required inputs, and an output schema, so the description is adequate for basic invocation. It lacks domain context about what a 'rate band' is or how it differs from rate cells, but this is a moderate gap given the low complexity.

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 100%, with limit and offset both clearly documented in the schema itself. The description does not need to repeat parameter details, so the baseline score of 3 is appropriate.

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 and resource: 'List Rate Bands'. It is not a tautology, but it does not differentiate this endpoint from closely related siblings such as list_rate_cells or list_tutor_tiers, so it falls short of the top score.

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 tool versus alternatives like list_rate_cells or when pagination is necessary. The description gives no context about the intended scenario or exclusions, leaving the agent to infer usage from the name alone.

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