List Page Rules

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the description's 'Read operation' sentence merely restates the safety profile. It discloses nothing new about auth needs, pagination, or result volume that the annotations don't cover.

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?

Two short sentences, front-loaded with the core action, with no padding. The second sentence is somewhat redundant against the readOnlyHint annotation, keeping it out of 5 territory.

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, 6 parameters covering filtering and sorting, and no required parameters, the description should explain the listing/filter behavior and return shape. It does neither, leaving the agent with only a one-line summary for a moderately complex list tool.

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 83%, so the schema already documents match, order, status, direction and account. The description contributes no additional meaning about these filters or their interaction, which is the baseline 3 posture when schema does the heavy lifting.

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?

States a specific verb (Fetches) and resource (Page Rules) scoped to a zone, which lets an agent distinguish it from the singular sibling get_page_rule. It falls short of a 5 because it never explicitly routes away from that sibling or names any alternative.

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 offers no when-to-use guidance, no reference to get_page_rule for single-rule retrieval, and no mention of the filtering/sorting context implied by its 6 parameters. An agent must infer placement entirely from the name.

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