list_rulesets

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It clarifies the return content (metadata only, no rules) and implicitly indicates it is a read operation (list). However, it does not detail pagination, rate limits, or response format, which is a gap for a list operation with no other behavioral metadata.

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 sentences long, with the primary action and core information in the first sentence, and the alternative routing in the second. Every word serves a purpose; no filler or 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?

The tool is simple (one parameter) and the description covers its main behavior and routing to a sibling. However, because there is no output schema and no annotations, it could be more complete by mentioning that the response is a paginated list or any default limits, and note that it is read-only. Still, for a list operation, the current description is sufficient for basic usage.

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 input schema has 100% coverage and describes 'zone_id' as 'The ID of the zone'. The description adds no further meaning about the parameter, so it adds no extra semantic value beyond the schema. The baseline 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 ('List all rulesets'), the resource ('for a Cloudflare zone'), and the key distinction from get_ruleset ('without individual rules'). It is specific and unambiguous, fully distinguishing it from the sibling tool.

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 explicitly directs users to use get_ruleset when they need to inspect individual rules, providing a clear when-not-to-use scenario. It lacks mention of alternative list tools (like list_waf_managed_rulesets) but still offers sufficient usage context.

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