domains_list_user

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

With no annotations, the description carries the disclosure burden. It adds useful behavior beyond the name: the username is optional, empty means the current session, and the underlying API call is CMD_API_SHOW_DOMAINS. It does not disclose permission requirements or error behavior, but 'List' signals a read-only operation and the output schema covers the return shape.

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?

Two short, front-loaded sentences. No filler; the purpose line is immediately followed by the only parameter explanation.

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 one-optional-parameter list tool with an output schema, the description is nearly complete. The ambiguous '(admin)' placement is the main weakness—it could be read as describing a user who is an admin rather than the admin-only ability to pass a username. This keeps it from being fully self-explanatory.

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 coverage is 0%, so the description must explain the username parameter. It does: optional account, empty default maps to current session, and underlying API call. It could add that specifying a username is an admin capability, but for a single optional parameter this is sufficient.

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 action ('List') and resource ('domains'), and scopes it to a specific account or the current one. This distinguishes it from sibling domain tools like domains_create, domains_delete, subdomains_list, and domain_pointers_list. The parenthetical '(admin)' clarifies the two operating modes.

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 description gives an implicit use case: use it to list domains for the current session, or for a named user when operating as an admin. It does not explicitly name alternatives or state when not to use it, leaving routing largely to the tool name and sibling set. Score 3 reflects implied but not explicit guidance.

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