Delete Allowed Domain

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered; the description adds real beyond-annotation detail: the exact permission scopes required, delegated-token authorization semantics, and the confirm=true gate. The trailing 'May share access, notify people or incur provider charges' is generic boilerplate with less value.

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 purpose is front-loaded in one clean sentence, but the large fenced permission block and the generic trailing caveat inflate the text without adding tool-specific 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?

For a destructive single-resource delete with full annotation coverage and no output schema, the description supplies the key missing operational facts (permissions, confirmation gate). Nothing critical is missing, though it could clarify where a deleted domain disappears from (e.g., the allowed-domains list).

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 description coverage is 100%, so baseline is 3. The description restates the confirm=true requirement but adds no syntax, format, or edge-case meaning for domain/account beyond what the schema already documents.

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 and resource: 'Deletes an allowed domain from the account.' It is easily distinguished from siblings like create_allowed_domain, get_allowed_domain, and list_allowed_domains by the delete verb, though it never names them explicitly.

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?

Usage context is implied and constrained by prerequisites: the required token permissions and the 'Requires confirm=true for the requested mutation' rule tell the agent when the call is permissible. However, there is no explicit when-to-use/when-not guidance or routing to alternative siblings.

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