List Worker Domains

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive. The description adds account scoping and optional filters, but does not disclose pagination, response shape, or other behavioral details beyond what annotations and schema imply.

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 concise, front-loaded sentences. The first states the verb and resource; the second covers filtering options. No filler or redundancy.

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 read-only list tool with comprehensive annotations and complete schema descriptions, the description is mostly sufficient. It lacks explicit output details (e.g., pagination/response format), but the tool's purpose is straightforward and context signals are strong.

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 covers all 5 parameters with individual descriptions (100% coverage). The description summarizes the main filter dimensions (Worker name, hostname, zone) but omits 'environment', adding marginal value beyond the schema.

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?

Clearly states it lists custom domains attached to Workers in the account, using a specific verb and resource. This distinguishes it from sibling add/delete/set domain operations and other worker-related tools.

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?

Provides optional filter context (Worker name, hostname, zone) that clarifies when to apply filters. It does not explicitly name alternatives, but the read-only list vs mutate distinction is implicit from sibling names.

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