List domains

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

With no annotations, the description carries the full burden. It clarifies that the operation returns all domains with their configuration data, which implies a read-only action and gives an expectation of output content. It does not mention pagination, limits, or authentication, but for a list operation this is reasonable transparency.

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, well-structured sentence that states the action, resource, and included details without any redundancy or filler. It is front-loaded with 'List all' and wastes no 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?

For a list tool with no parameters and no output schema, the description fully covers what the tool does and what the response will contain. The sibling tools cover creation, update, verification, and singular fetch; this description clearly completes the list function. No critical gaps are evident.

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 zero parameters, so no semantic explanation is needed. The schema coverage is complete (100% of nothing). The baseline for zero parameters is 4, and the description appropriately does not attempt to add parameter details.

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 uses a specific verb ('List') and identifies the resource ('all DeepTap domains for the account'), clearly distinguishing it from siblings like get_domain (singular) and create_domain. It also specifies the included details (iOS/Android config, AASA/assetlinks URLs), making the scope unmistakable.

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 phrase 'List all ... for the account' conveys the context: use this to enumerate all domains rather than fetching a specific one via get_domain. It does not explicitly mention when not to use it or name alternatives, but the distinction from the singular get_domain is implied by 'all domains'.

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