liara_list_zones

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

No annotations are provided, so the description carries the full burden. It states the action ('List all DNS zones') but doesn't disclose behavioral traits like pagination behavior (implied by parameters but not described), rate limits, authentication requirements, or what 'all' entails (e.g., includes deleted zones?). This leaves gaps for safe and effective use.

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, efficient sentence ('List all DNS zones') that is front-loaded with the core action. There is no wasted verbiage, making it easy to parse and understand immediately.

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?

Given the tool's low complexity (a list operation with no output schema and no annotations), the description is minimally complete but lacks depth. It covers the basic purpose but misses behavioral details (e.g., pagination, return format) that would help an agent use it correctly without annotations or output schema.

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 schema description coverage is 100%, with clear descriptions for all 4 parameters (page, perPage, limit, offset). The description adds no additional parameter semantics beyond what the schema provides, which is acceptable given the high coverage, resulting in a baseline score of 3.

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 all DNS zones' clearly states the verb ('List') and resource ('DNS zones'), making the purpose immediately understandable. It distinguishes from siblings like 'liara_get_zone' (singular retrieval) and 'liara_create_zone' (creation), though it doesn't explicitly mention this distinction.

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 versus alternatives. While the name implies listing all zones, there's no mention of filtering options, prerequisites, or comparisons to other list tools (e.g., 'liara_list_dns_records' for records within zones). The description lacks context for decision-making.

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