list_domains

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

The description adds that the tool returns verification status, which is a behavioral detail beyond what annotations provide. Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, so the description complements them without repeating.

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 sentence that is front-loaded with the core purpose. Every word is necessary, and there is no extraneous information.

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 the tool's simplicity (no parameters, no output schema), the description adequately conveys what the tool does and what it returns. It could optionally hint at the response structure (e.g., array of objects), but the core information is present.

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 tool has zero parameters, and schema coverage is 100%. Per the scoring guidelines, 0 parameters defaults to a baseline of 4. The description does not need to explain parameters, and it adds no extra semantic information.

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 action ('List'), the resource ('all domains'), and a specific attribute ('verification status'). This fully distinguishes it from sibling tools like get_domain (single domain) or create_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?

No guidance is provided on when to use this tool versus alternatives such as get_domain (for a single domain) or verify_domain (for checking a specific domain). The description implies the tool is for listing all domains but offers no exclusions or context.

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