domainForwardSubDomainDelete

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 only says 'Delete a subdomain forward' and does not mention irreversibility, permission requirements, side effects, or whether related records are also removed. The API reference link is not a substitute for explicit behavioral detail.

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, direct sentence with no filler. The API reference link is the only addition and is relevant for external details. It is appropriately concise and front-loaded.

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 a simple two-parameter delete operation and the description plus schema covers the core invocation. However, with no output schema and no annotations, information about return values, success/failure behavior, and when this endpoint is appropriate is missing. It is adequate but not complete.

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 coverage is 100%, so the schema already documents both parameters. The descriptions 'Domain' and 'Subdomain label' are minimally useful but add no additional meaning beyond the schema. This meets the baseline for schema-driven parameter understanding.

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 verb ('Delete') and a clear resource ('subdomain forward'), making the tool's function immediately obvious. It also differentiates itself from sibling tools like domainForward and domainForwardSubDomain, which likely create or manage forwards rather than delete subdomain forwards.

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 provided about when to use this tool versus alternatives. Sibling tools such as domainForwardSubDomain and domainForward are related but the description does not explain when to choose domainForwardSubDomainDelete over them.

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