list_catalog_zones

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

With no annotations provided, the description is fully responsible for disclosing behavioral traits. It only states the list action and does not mention pagination limits, return format, whether archived zones are included or excluded, or any other side effects. This leaves significant behavioral ambiguity for a tool that could interact with a large dataset.

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 redundant information. It efficiently conveys the purpose without any fluff, earning a top score for conciseness.

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 simple listing tool with full schema coverage, the description is minimally adequate. However, it does not mention the output format, default pagination behavior (though the schema does), or how it differs from the many sibling zone tools. More context would help the agent choose this tool confidently, but given its simplicity, a score of 3 is fair.

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?

The input schema provides complete descriptions for both parameters (limit and offset), achieving 100% schema description coverage. The tool description adds no additional parameter semantics, so the baseline score of 3 is appropriate per the rubric.

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 the action 'List all catalog zones' with a specific resource type, and the parenthetical 'for product/retail ad serving' adds domain context that helps it stand out from generic zone listing tools like list_zones and vast_list_zones. This is a specific verb+resource pair that satisfies the top score even without an explicit sibling reference.

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 implies usage by naming the resource type, but it does not explicitly state when to use this tool versus alternatives, nor does it provide any exclusions. The 'for product/retail ad serving' hint gives limited context, but there is no guidance on when not to use it or which sibling tools might be more appropriate for different zone types.

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