web_subdomain_delete

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 conveys that the operation is destructive, but it does not mention irreversibility, cascading effects on DNS or web configuration, required permissions, or whether confirmation is involved. This is a meaningful gap for a delete operation.

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 wording. It earns its place by stating the core operation efficiently, though it is terse and omits context that would be useful in a tool description.

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-parameter, fully schema-documented tool, the core call signature is complete. However, because it is a destructive mutation with no annotations and no output schema, the description should also mention side effects or prerequisites to be fully contextual. It is minimally viable but has clear gaps.

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 covers the single parameter subdomain_id with 100% coverage and a reasonable description, so the schema already provides the necessary semantics. The tool description adds no additional parameter-level meaning, which is acceptable under the baseline for high schema coverage.

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 states a specific action, 'Delete', on a specific resource, 'subdomain', which clearly distinguishes it from the sibling tool web_domain_delete that operates on parent domains. It also logically complements web_subdomain_add. The purpose is unambiguous.

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 such as web_domain_delete or web_subdomain_add. It does not state prerequisites, whether the subdomain must belong to a web domain, or any conditions under which deletion should be avoided.

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