delete_subdomain

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

With no annotations, the description must disclose behavior. It states that the URL stops serving content, which is a key effect. However, it does not mention whether the subdomain becomes available for reuse, if there are any irreversible consequences, or authorization requirements (e.g., ownership).

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 short sentences with no wasted words. The second sentence adds value by stating the effect. Could be slightly more structured (e.g., indicating return value) but is appropriately concise.

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 simple deletion tool with no output schema, the description covers purpose and effect. However, it lacks details on return behavior, error conditions, and prerequisites. Given the absence of annotations, more completeness would be beneficial.

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?

Both parameters have descriptions in the schema (100% coverage). The tool description does not add any extra meaning beyond what the schema provides, so it meets the baseline but does not improve 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 'Release a custom subdomain' clearly states the action and resource. The added detail 'The URL will stop serving content' clarifies the consequence. It distinguishes from siblings like 'claim_subdomain' and 'add_custom_domain', but does not explicitly differentiate from 'remove_custom_domain' (which may have similar semantics).

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 on when to use this tool vs alternatives such as 'remove_custom_domain' or 'disable_sender_domain_inbound'. The description does not mention prerequisites, side effects, or context for invocation.

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