list_user_agent_rules

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'List', which implies a read operation, but does not explain pagination behavior, whether all rules are returned, or any auth/permisions context. For a list tool with zero annotation coverage, this is insufficient.

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 a single sentence with zero wasted words. It clearly front-loads the action and resource, and every word contributes to conveying the tool's purpose.

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 one required parameter and no output schema, the description provides the minimal core purpose but omits details like pagination, response shape, and edge-case behavior. The agent can probably call the tool correctly, but the description does not fully equip it for post-call interpretation or for handling large result sets.

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%, with the single zone_id parameter fully documented as 'The zone ID'. The description's phrase 'for a zone' loosely reinforces that the parameter is the zone identifier, but adds no meaningful semantic detail beyond what the schema already provides, so 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 a specific verb ('List'), a distinct resource ('user agent blocking rules'), and a scope ('for a zone'). It differentiates itself from sibling tools like list_firewall_rules and list_ip_access_rules by naming a unique resource type, so an agent can identify what this tool does without opening the schema.

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 use case is implied by the verb and resource: use when needing to list user agent blocking rules for a zone. However, the description provides no explicit guidance about when to prefer this tool over related rule-list tools, nor does it mention any exclusions or prerequisites beyond the zone context.

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