list_subdomains

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

The description discloses the main behavior (listing all registered subdomains with DNS records) without contradictions. It lacks details on pagination or record scope but is adequate for a zero-parameter tool.

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 concise sentence that directly conveys the tool's purpose with no wasted words.

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 no parameters and no output schema, the description provides enough context for a simple list operation. It could mention scope (e.g., active only) but is sufficiently 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?

There are no parameters, and the description adds no parameter details, but the baseline for zero parameters is 4. Schema coverage is 100%, so no additional information is needed.

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 it lists registered subdomains with their DNS records, using a specific verb and resource. It distinguishes well from sibling tools like list_domains and list_requests.

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 when to use the tool (to see all subdomains) but does not provide explicit guidance on when not to use it or mention alternatives like check_subdomain for specific subdomains.

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