subdomains_list

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

The description identifies the operation as a list/read, which implies no side effects, but it does not state permission requirements, impersonation behavior, pagination, or failure modes. With no annotations, the description carries the disclosure burden and provides only the bare verb.

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 extremely concise, with the core purpose front-loaded in the first sentence and a compact Args block. There is no filler or redundant 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?

The tool is simple and an output schema exists, but the description lacks usage guidance, exclusions, and explanation of impersonation behavior. It is minimally adequate yet leaves important selection and permission questions unanswered.

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 0%, and the description compensates by glossing both parameters: 'domain: Parent domain' and 'impersonate: Owning user'. This adds some meaning beyond the schema property names, but the impersonate semantics remain ambiguous, especially regarding the effect of an empty default.

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 the specific verb 'List' with the resource 'subdomains of a domain', making the core operation unambiguous. It is clearly distinct from sibling tools like subdomains_create and subdomains_delete, and no other sibling performs this exact read.

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 given on when to use this tool versus alternatives. The description does not mention related tools, admin versus user context, or situations where another endpoint would be more appropriate.

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