List Url Rewrite Rules Tool

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

The readOnlyHint annotation already tells the agent this is a safe read, so the description contributes essentially nothing behavioral on its own. It does not disclose whether results are paginated, whether they are zone-scoped, or whether an empty result is possible. No added context beyond the annotation.

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?

One short sentence with zero filler and no preamble — nothing to trim. It is front-loaded by nature, though the brevity comes from under-specification rather than disciplined editing.

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?

An output schema exists, so return values need no explanation, and the lone parameter is fully documented in the schema. What is still missing is scope and volume context — whether all rules in the zone are returned or a subset, and how the listing relates to the set_ sibling.

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 the single zone_id parameter carries its own format note ('32-character hex string'), so the schema does the full job. The description adds no parameter meaning, which is the expected baseline of 3 when coverage is complete.

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 'List URL rewrite rules.' is a near-verbatim restatement of the tool name and title, which is the textbook tautology case. It identifies a verb and resource, but adds no scope, no filtering behavior, and no differentiation from siblings such as set_url_rewrite_rules_tool.

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?

There is no when-to-use guidance, no mention of prerequisites like a required zone, and no pointer to the paired write tool. The agent must infer usage purely from the name. Nothing is misleading, but nothing is stated either.

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