Get Domain List

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

With no annotations, the description carries the full burden. It indicates a read operation but discloses no additional behavior such as pagination, scope details, or return format. It is a minimal but safe description; could be improved by noting that it is non-destructive and returns domain details.

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, front-loaded sentence with no redundant words. It is concise, though slightly under-specified; adding a few more details would not hurt, but it does not contain unnecessary content.

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?

This is a simple, parameterless list tool, but the description lacks information about the return structure or potential pagination limits. Given no output schema exists, the description should at least mention the response format or domain properties returned. The presence of a paginated sibling suggests possible limitations not addressed here.

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 the schema is empty with 100% coverage. There is nothing to describe, so the baseline of 4 applies. The description appropriately omits 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 clearly states the verb 'List' and the resource 'all domains in your portfolio,' making the purpose unambiguous. It distinguishes from related tools like agency_domains_list by specifying user-owned domains, though it doesn't explicitly mention the paginated sibling.

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 list_all_domains_paginated or agency_domains_list. The description implies usage via the 'List all' wording, but there is no explicit context or exclusion.

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