list dns domains

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds that it executes a verified command, but does not describe return format or pagination. With annotations carrying the safety profile, this is adequate but not rich.

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?

One sentence with no fluff, front-loading the action. It is appropriately concise for a simple list operation, though it could include parameter hints without much length.

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?

The tool is simple, annotations are strong, and an output schema exists. However, the description doesn't explain the 'user' parameter or 'format' option, leaving some gaps. Adequate for a minimal definition but could do better.

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 has 0% description coverage, and the description does not mention parameters at all. It fails to explain the required 'user' parameter or the 'format' enum, leaving the agent without any guidance beyond the schema's structural constraints.

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?

States a specific verb and resource ('List a user's DNS zones'), which clearly distinguishes it from sibling tools like list_web_domains and list_mail_domains. The mention of the underlying command ('v-list-dns-domains') adds specificity.

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?

Provides clear context by specifying the scope (a user's DNS zones). However, it does not explicitly mention alternatives or exclusions, such as when to use list_dns_records or get_dns_domain instead.

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