list_domains

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

With no annotations, the description carries full burden. It mentions the output includes specific fields, but does not explicitly state it's read-only or that no side effects occur. The name 'list' implies non-destructive behavior, but the description could be more explicit about the tool's impact.

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 two sentences, containing all essential information without redundancy. It is front-loaded with the main action and provides key details efficiently.

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 5 parameters with full schema coverage and no output schema, the description adequately covers the purpose and output fields. It mentions paging and search, though it could detail pagination behavior. Still, it is fairly complete for a list tool.

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 descriptions for each parameter. The tool description adds no extra semantics beyond the schema; it only provides a high-level overview of the tool's output. 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 uses a specific verb 'List' and resource 'domains in the account', and enumerates the fields returned (creation/expiry dates, lock status, auto-renew, WhoisGuard status). It clearly distinguishes from siblings like get_domain_info which targets a single domain.

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 viewing domain lists with filtering and paging, but does not explicitly state when to use this tool versus alternatives (e.g., check_domains for availability, or get_domain_info for detailed info on one domain). No exclusions or prerequisites are mentioned.

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