list_page_shield_policies

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

No annotations are present, so the description carries the full behavioral burden. The verb 'List' implies a read-only operation, but the description says nothing about pagination, response shape, scope, or other behavioral expectations.

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, front-loaded sentence with no filler. It is minimal, but it is genuinely concise rather than verbose, and every word in it contributes to stating the operation.

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?

With no output schema and no annotations, this one-line description leaves the agent to infer return shape, usage context, and how to choose this over the many related Page Shield and listing tools. It is not complete enough for confident tool selection and invocation.

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%, and zone_id is already documented as 'The zone ID'. The description adds no additional parameter meaning, but the schema fully covers the single parameter, so the baseline 3 applies.

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 states a clear verb and resource: it lists Page Shield policies. It distinguishes at the noun level from sibling tools like list_page_shield_scripts and list_page_shield_connections, though it does not explicitly contrast with them.

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 provided on when to use this tool instead of related Page Shield tools such as get_page_shield_settings, list_page_shield_scripts, or list_page_shield_connections. There is also no mention of prerequisites or zone-scoping context.

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