Delete Subdomain

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

The description adds no behavioral context beyond the annotations. The destructiveHint: true annotation already signals the destructive nature, but the description does not disclose specifics such as whether the deletion is permanent, irreversible, or has cascading effects on associated resources. No additional transparency is provided.

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 sentence and is concise, but it is also under-specified, essentially repeating the title. It is not excessively padded, but it lacks any informative structure or supplementary details that would earn a higher score. It is appropriately short, but conveys minimal value.

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?

Given the tool's destructive nature and the lack of an output schema, the description is incomplete. It does not explain the effect of deletion, edge cases, or any required context for safe usage. The annotation and schema cover basic safety and parameters, but the description fails to provide a complete picture for an AI agent.

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: 'domain' is Website domain, 'username' is Hosting account username, 'subdomain' is Subdomain to delete. The description itself adds no further meaning or clarification, but the schema fully documents each parameter, so a baseline of 3 is appropriate.

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 'Delete a subdomain.' is a direct restatement of the tool name and title (hosting_subdomains_delete / Delete Subdomain), providing no additional clarification or distinction beyond what is already obvious. While it is not misleading, it is a tautology, which aligns with a score of 2.

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 offers no guidance on when to use this tool versus alternatives (e.g., hosting_subdomains_list or hosting_subdomains_create), nor does it mention any prerequisites, exclusions, or special conditions. It simply states the action with no contextual usage information.

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