cf_list_gateway_rules

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

No annotations are provided, so the description carries the burden. It specifies the HTTP method (GET) and that it uses a filter, which implies a read-only operation. However, it does not explicitly state safety (e.g., no side effects) or mention rate limits, pagination, or required permissions.

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 concise with four sentences: a clear purpose statement, parameter list with defaults, and the API endpoint. Every sentence adds value, and the structure is front-loaded with the main action.

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 that an output schema exists (so return values are documented elsewhere) and the tool is a simple list operation, the description covers the key aspects. However, it omits information about pagination (common for list tools) and whether additional filters are supported, which would improve completeness.

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?

With 0% schema coverage, the description adds meaning for both parameters. For 'rule_type', it enumerates the valid values ('dns', 'network', 'http') and documents the default, going beyond the schema. For 'account_id', it merely repeats 'account ID', which adds little. Overall, it provides useful but not comprehensive parameter context.

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 resource (Cloudflare Gateway rules) with specific subtypes (DNS, network, HTTP). It distinguishes from sibling tools which list other resources, making the purpose unambiguous.

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 implies usage for listing gateway rules and provides parameter details, but it does not offer explicit guidance on when to use this tool versus alternatives, nor does it state when not to use it.

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