ecp_dns_list_records

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'List DNS records,' which implies a read operation, but it doesn't disclose whether the list is paginated, sorted, filtered, or what happens if the domain doesn't exist. For a read tool, this is a moderate gap but not a contradiction.

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 short sentence that is front-loaded with the action and resource. It is concise and easy to parse, though it could add a bit more useful context without becoming verbose.

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 has one required parameter, no output schema, and no annotations, the description is too thin. It doesn't explain the return format, error behavior, or any domain validation rules. An agent would need to guess or call the tool to learn basic behavior.

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%, and the description only mentions 'a domain's zone' without explaining the format or semantics of the 'domain' parameter. It doesn't clarify whether the domain should include 'www', a trailing dot, or a subdomain. The description adds minimal value beyond the schema's bare parameter name.

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 states a specific verb and resource: 'List DNS records for a domain's zone.' This clearly identifies the operation. However, it doesn't explicitly distinguish itself from sibling tools like ecp_dns_add_record or ecp_dns_delete_record, though the verb 'list' makes the distinction fairly obvious.

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 about when to use this tool versus alternatives. There is no mention of prerequisites, such as whether the domain must exist or be managed by the system, nor any exclusions. The context signals show many DNS-related siblings, but the description doesn't help an agent choose among them.

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