List all domains

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered externally. The description adds that results are paginated and scoped to the authenticated workspace, but says nothing about default page size, archived-domain handling, or how filtering affects results. Useful but thin given annotations carry the safety profile.

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?

A single efficient sentence with the operation front-loaded and no filler. It is appropriately sized for a simple list tool, though it leaves little room for the scoping and pagination detail the other dimensions call for.

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 zero-required-parameter list tool with full schema coverage and complete annotations, this is minimally adequate. However, it omits any note on pagination defaults, result ordering, or how the search/archived filters behave, which an agent would benefit from when composing calls.

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 description coverage is 100%, so all five parameters (page, search, account, archived, page_size) are already documented in the schema with defaults and bounds. The description's only param-relevant contribution is the word 'paginated', which adds no detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Retrieve a paginated list of domains') with scope ('authenticated workspace'), so the agent knows exactly what operation this performs. It does not differentiate itself from siblings like list_accounts or delete_domain, relying on the name alone for routing.

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?

There is no guidance on when to use this tool versus alternatives such as list_accounts or list_links, nor any mention of prerequisites or expected context. The only usable signal is 'authenticated workspace', which is a scope statement rather than usage guidance.

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