list_subdomains

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to explain what data is returned (array of strings? objects?), whether the operation is read-only or rate-limited, or what happens if the domain is invalid. The two-word description provides zero behavioral context.

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?

While extremely brief (two words), this represents under-specification rather than efficient conciseness. As noted in the rubric, 'Process' is under-specification, not conciseness. The description wastes no words but fails to earn its place with meaningful 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?

Despite having only one parameter and no output schema, the description is incomplete. It should explain the return format or what 'listing' entails (active DNS records? registered subdomains? historical data?). For a tool with no annotations, more context is required to compensate.

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 input schema has 100% description coverage with the 'domain' parameter documented as 'Domain name'. The description adds no semantic information about the parameter (e.g., whether it should include protocol, be a root domain, or format requirements). With full schema coverage, the baseline score is 3.

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 'List Subdomains' is a tautology that merely restates the tool name 'list_subdomains'. While it technically identifies the verb (List) and resource (Subdomains), it fails to distinguish scope or provide any specific detail about what constitutes a subdomain in this context or what the listing entails.

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?

There is no guidance on when to use this tool versus alternatives, prerequisites (e.g., whether the domain must be verified), or what to do if no subdomains exist. The absence of sibling tools does not excuse the lack of usage context for this single-parameter tool.

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