hosting_listWebsiteSubdomainsV1

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

Description defines operation as read-only (retrieve) and lists returned attributes. With no annotations, it adequately communicates scope. Omits pagination or potential empty responses, but acceptable for a simple list.

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 concise sentences, front-loaded with action and outcome. No redundant information.

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?

Lacks output schema; description partially covers return fields but doesn't specify if additional fields exist or format. For a list endpoint, this is adequate but could be more comprehensive.

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?

100% schema coverage sets baseline at 3. Description adds minimal detail beyond parameter names and basic schema descriptions (e.g., 'selected website'). Does not clarify 'username' parameter role.

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?

Description clearly states it retrieves subdomains for a specific website, specifying included data (parent domain, root directory). Differentiates from sibling create/delete subdomain tools.

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?

Explicitly says 'Use this endpoint to inspect subdomain configuration', providing clear usage context. Lacks explicit when-not-to-use or alternatives, but sibling list/management tools are easily distinguished.

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