dns_list_zones

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

With no annotations and a description that only says 'List DNS zones,' there is no disclosure of behavior like pagination, filtering, or ordering. The parameters page, per_page, name, and search_name hint at capabilities, but the description does not explain them.

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 very concise but at the expense of completeness. Three words do not provide enough information for effective use, especially given the number of parameters and the lack of schema descriptions.

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 that an output schema exists but the description does not mention it, and the input parameters are undocumented, the tool is incomplete for an AI agent. It does not convey pagination or filtering capabilities.

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 0%, meaning no parameter is documented in the schema. The description adds zero parameter context. For a tool with 4 parameters, this is a critical gap.

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 DNS zones' clearly states the verb and resource, but it does not differentiate from sibling tools like dns_get_zone or dns_list_records, which is a missed opportunity for a higher score.

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 provides no guidance on when to use this tool versus alternatives such as dns_get_zone for a single zone or dns_export_zone_file for export. This omission hurts usability.

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