cf_list_custom_rules

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

As a read-only listing tool, the description conveys non-destructive behavior and specifies the output normalization, but lacks details on error handling or 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?

Two sentences efficiently convey purpose, equivalent tool, and return shape without redundancy.

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 the single parameter and the presence of an output schema, the description adequately covers the tool's function and result shape, though error handling is omitted.

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 schema has 0% coverage for parameters, and the description adds no explanation for the required zone_id parameter, leaving its meaning and source unclear.

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 it lists custom WAF rules for a zone, distinguishing it from the similar sibling cf_get_entrypoint_ruleset by noting the normalized return shape.

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?

Explicitly describes it as a convenience equivalent to cf_get_entrypoint_ruleset with a normalized output, guiding the agent to choose this when a standardized return shape is desired.

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