list_rate_limits

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose response contents ('thresholds, matching criteria, actions, and bypass rules') and the 'list' verb implies a read-only operation, but it does not address pagination behavior, ordering, errors, or permission requirements.

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?

Three sentences, each earning its place: the action, the response contents, and a concrete use case. The primary purpose is front-loaded and there is no filler or repetition of schema information.

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?

For a paginated list tool with fully documented parameters, the description is nearly complete: it states the purpose, what the response contains (compensating for the absent output schema), and a concrete use case. The only gaps are the lack of explicit sibling routing to get_rate_limit and no explicit read-only/authorization disclosure, which is mitigated by the 'list' verb.

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 all three parameters (zone_id, page, per_page) already documented including defaults and max. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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 states a specific verb and resource: 'List rate limiting rules for a Cloudflare zone.' It further specifies what is returned ('thresholds, matching criteria, actions, and bypass rules'), which distinguishes it from the singular get_rate_limit sibling and from list_firewall_rules/list_rulesets.

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?

The description provides clear use context: 'useful for checking brute-force protection and identifying rate-limited traffic.' However, it does not name alternatives or state when not to use this tool, so the agent must infer the distinction from sibling names like get_rate_limit.

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