dns_list_domains

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

No annotations are provided, so the description carries full burden. It discloses the output format options but does not explicitly state that the operation is read-only, nor does it mention any permissions, rate limits, or side effects. The behavior is simple and mostly clear, but lacks explicit safety or side-effect disclosure.

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 concise, front-loads the main purpose, and uses a clear structure with Args and Returns sections. No redundant or filler content; every sentence serves a purpose.

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?

With an output schema present, detailed return-value documentation is not necessary. The description explains the input parameter sufficiently and states what the operation returns. The tool is simple, and the description is complete enough for an agent to call it correctly, though it could optionally mention pagination or other constraints.

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 description thoroughly explains the only parameter 'format', detailing both allowed values ('compact' and 'json') and what each returns, with the default noted. This goes beyond the bare schema which only specifies type and default, providing meaningful semantics for the agent.

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 all DNS domains in your Vultr account.' It clearly distinguishes itself from sibling tools like dns_list_records (records) and dns_get_domain (single domain) by scope and action.

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 implies usage for listing all domains, but does not explicitly mention alternatives or when not to use it. No exclusionary guidance is provided, but the purpose is unambiguous enough to infer correct usage.

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