Get domain list

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

The readOnlyHint and destructiveHint annotations already establish that this is a safe read operation. The description adds the account-scoped 'all domains' behavior, but it does not go further to describe response format, pagination, or any other runtime behavior. This is adequate but not rich.

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 short and front-loaded with the core action. The second sentence, 'Use this endpoint to view user's domain portfolio,' is slightly redundant with the first but still reinforces the purpose without adding bloat.

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 parameterless, read-only list operation with no output schema, the description provides sufficient context: it returns domains associated with the account. It could mention pagination or response fields, but given the tool's simplicity and annotation coverage, this is a minor gap.

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%, so the description is not required to explain parameters. Per the baseline rule for 0-parameter tools, this is handled appropriately; there is nothing missing.

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 and resource: 'Retrieve all domains associated with your account.' It clearly states the tool lists account-level domains. However, it does not explicitly distinguish itself from sibling tools like agency-hosting_listDomainsV1 or domains_getDomainDetailsV1, so it falls short of full differentiation.

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?

'Use this endpoint to view user's domain portfolio' gives clear context for when to call the tool. It does not, however, mention when not to use it or point to alternatives such as domains_getDomainDetailsV1 for individual domain details.

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