namecheap_list_domains

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 does not state that the operation is read-only or explain pagination behavior; claiming 'List all domains' is misleading because the page/pageSize parameters mean a single call may return only a subset. This is a notable omission that could cause incorrect agent behavior.

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, clear sentence that directly communicates the tool's purpose and key returned details. It contains no unnecessary words and efficiently front-loads the core action ('List all domains').

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 description lists the returned fields, which is helpful given there is no output schema. However, it omits important context about pagination and defaults (e.g., pageSize=100), which directly affects the accuracy of the 'all domains' claim. The tool is simple, but the missing caveat prevents it from being fully complete.

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?

Both parameters (page and pageSize) are fully documented in the schema with default values and maximum, covering 100% of the parameter description. The tool description adds no supplementary parameter information, so the schema is sufficient and the baseline score 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 clearly states the tool's action ('List all domains') and resource ('in your Namecheap account') and lists the specific details included in the output (expiration, auto-renew, lock status, DNS provider). This distinguishes it from sibling tools like namecheap_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 provides clear context for when to use the tool: to list all domains in the account. It does not explicitly mention alternatives, but the 'all domains' phrasing implies it is the right choice for broad listing, while the sibling namecheap_get_domain_info handles individual domains. Without explicit exclusions, it still offers adequate context.

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