list_firewall_rules

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action and the data returned, but it does not mention that this is a read-only operation (no side effects), or any prerequisites like required permissions. It also does not describe pagination behavior beyond what the schema implies. The description provides some context but lacks depth on response structure or potential errors. Given the read-only nature and common listing pattern, a 3 is appropriate.

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 two concise sentences. The first states the action and output, the second provides a use case. There is no fluff or redundancy, and the key information is front-loaded. Every sentence earns its place.

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 it's a simple listing tool with three parameters and no output schema, the description is mostly complete. It covers purpose, returned data, and a typical use case. It could mention that results are paginated (though the schema implies it) and how to interpret the returned rules (e.g., that expressions are in Cloudflare's syntax). But for a list operation, it provides sufficient context for an agent to call it correctly. The absence of explicit pagination guidance is a minor gap.

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 coverage is 100% – all three parameters have descriptive text (zone_id, page, per_page) in the schema. The description does not add meaning beyond what the schema provides, except implying that zone_id is the target of the listing. Since the schema covers the parameters adequately, the baseline of 3 is correct.

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 verb 'list' and resource 'custom firewall rules' for a Cloudflare zone. It also specifies the returned data (rule expressions, actions, priorities), distinguishing it from other list tools like list_rulesets or list_rate_limits. The context of 'custom' differentiates it from managed rules, providing clear purpose.

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 gives a clear use case: 'investigating which rules may be blocking or challenging traffic.' This implies when to use the tool. However, it does not explicitly mention alternatives or when not to use it, such as when needing a single rule (get_firewall_rule) or when working with managed rulesets. But the naming and context provide sufficient guidance for most agents.

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