domain_list

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

No annotations are provided, so the description carries the behavioral disclosure burden. It explicitly states 'Read-only' and describes what fields are returned and that filtering is supported. It does not mention pagination or response shape, but for a simple read-only list tool the core behavioral traits are covered.

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?

Two short sentences deliver the core purpose, returned fields, read-only nature, and filtering capability with no wasted words. The most important information is front-loaded.

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?

For a simple tool with three optional parameters and no output schema, the description is complete enough for an agent to invoke it correctly and understand what response fields to expect. It omits explicit pagination behavior, but the page/pagelimit parameter names and defaults make this inferable from the schema.

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 only 33%, with page and pagelimit lacking descriptions. The tool description's 'Filter by substring or TLD' adds little beyond the schema's domain parameter example and does not compensate for the undocumented pagination parameters.

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'), names the resource ('domains in the account'), and enumerates the returned fields (status, nameservers, renewal mode, expiry). It also clearly marks the operation as read-only, distinguishing it from sibling tools like domain_info or domain_check.

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 gives clear context: use this tool for account-level domain listing, with optional substring/TLD filtering, and it is explicitly read-only. It does not explicitly name alternative tools or provide when-not-to-use guidance, but the listing-vs-detail distinction is reasonably clear from context.

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