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 full burden of behavioral disclosure. The verb 'List' does imply a read-only operation and the parenthetical adds rule-category scoping, but nothing is disclosed about pagination, response shape, ordering, or whether all rules or a subset are returned. For a list endpoint with zero annotation coverage, this is a meaningful omission.

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, front-loaded sentence with zero filler: the verb 'List' and the resource appear immediately, and the parenthetical efficiently scopes the content. It earns slightly less than 5 because the brevity reads more like under-specification than deliberate compression, given the missing behavioral context captured in other dimensions.

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 calling contract is trivially simple — one required, fully documented parameter — so an agent can invoke it correctly. However, with no output schema and no annotations, the complete absence of any mention of response format or pagination leaves real gaps for a list endpoint, and the description does nothing to disambiguate among the many sibling ruleset tools.

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 description coverage is 100% — account_id is documented with 'The account ID' — so the baseline of 3 applies. The tool description adds no parameter-specific meaning beyond what the schema already provides, which is acceptable but does not enhance the agent's understanding of the parameter.

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 uses a specific verb ('List') and a clear resource ('Zero Trust Gateway rules'), with a parenthetical narrowing scope to DNS/HTTP/Network filtering. This helps distinguish it from sibling tools like list_gateway_locations and list_gateway_proxy_endpoints, though it does not explicitly name alternatives, and the many ruleset siblings (list_zone_rulesets, list_account_rulesets, list_firewall_rules) are only implicitly excluded.

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 explicit when-to-use or when-not-to-use guidance is given, and no alternative tools are named. The scope phrase 'Zero Trust Gateway rules (DNS/HTTP/Network filtering)' combined with the account_id parameter implies account-scoped usage, but given roughly a dozen rule-related siblings in the list, an agent receives no direct routing help to pick this over list_zone_rulesets or list_account_rulesets.

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