list_domains

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

With no annotations, the description carries full burden. It discloses pagination behavior (offset, 1000 per page), which is good. However, it doesn't state read-only nature, side effects, or output format, leaving gaps for an agent.

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 at two sentences, front-loading the purpose. The second sentence adds practical detail. No fluff, but backticks for `start` are unusual.

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 list tool with no output schema, the description is adequate but not complete. It covers pagination but not output structure or behavior of include_labels. Given the parameter count and complexity, more context would be beneficial.

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 explains the 'start' parameter for pagination offsets, adding meaning beyond the schema. However, it omits explanation for 'include_labels', which remains undocumented. With 0% schema coverage, partial compensation is provided.

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 'List all domains in the Porkbun account', specifying the action (list), resource (domains), and scope (all in account). This distinguishes it from sibling tools like get_domain (single domain) and list_dns_records.

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 implicitly suggests use for listing domains, but lacks explicit guidance on when to use it versus alternatives, or prerequisites. The pagination note is helpful, but no 'when not to use' or reference to siblings.

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