list_cloud_connector_rules

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

No annotations are provided, so the description carries the full disclosure burden. It states the read-style 'List' action and zone scope, but discloses nothing about pagination, ordering, filtering, response shape, or whether any side effects occur.

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?

A single, grammatically complete sentence with no filler or restatement beyond the core information. It is efficient, though not as front-laded with additional context as a richer description could be.

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 tool with no annotations and no output schema, the description is underspecified. It doesn't explain what cloud connector rules are, how the list is returned, or how this list endpoint differs from related rule-listing endpoints; an agent would need external knowledge to call it confidently.

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?

Parameter schema coverage is 100%: zone_id is described as 'The zone ID', and the tool description echoing 'for a zone' adds no new format or constraint details. Baseline 3 applies because the schema already documents the only parameter sufficiently.

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?

Uses a specific verb ('List'), resource ('cloud connector rules'), and scope ('for a zone') in a complete, unambiguous statement. It doesn't explicitly differentiate from sibling rule-list tools like list_zone_rulesets or list_firewall_rules, though the resource name is distinct.

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?

No guidance is given on when to use this tool versus the many sibling list_*_rules tools. The description only restates the basic purpose; it provides no scenarios, prerequisites beyond zone_id, or alternatives.

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