dnsimple_list_zonesList the DNS zones in the account, with pagination and optional filters. API: GET /{account}/zones.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-based). | |
| sort | No | Sort order, e.g. "name:asc", "id:desc". | |
| per_page | No | Results per page (max 100). | |
| name_like | No | Filter to zones whose name contains this substring. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, so description is not required to state idempotence. The description adds value by mentioning pagination, filters, and the specific API endpoint, which are behavioral details beyond annotations.
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?
Single sentence with clear verb-object structure and API reference. No redundancy or unnecessary words.
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?
No output schema, and description does not explain return format (e.g., list of zones, pagination metadata). Also missing default sorting or ordering behavior. A list operation should describe the response shape.
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 coverage is 100% with each parameter described in the schema. The description generically mentions 'optional filters' but does not elaborate on parameter behavior beyond the schema, so baseline of 3 is appropriate.
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 identifies the action (list), resource (DNS zones), and scope (account). It also mentions pagination and filters, distinguishing it from sibling tools like list_domains.
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 on when to use this tool versus alternatives like dnsimple_get_domain or dnsimple_list_zone_records. Does not specify prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.