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

Annotations already indicate destructiveHint=true, so the destructive nature is known. The description adds valuable behavioral details: the need for confirm parameter set to DELETE, business permission checks, FREE business restriction, and the prerequisite call to check_business_tool_access. These go beyond the annotation.

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 relatively concise at 5 sentences, front-loading the core action. It includes multiple instructions but could be better structured into separate concerns (action, prerequisites, warnings). Still, no wasted words.

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 no output schema, the description covers prerequisites, permissions, and the grace-period warning. It mentions the need for a resubscribe link but does not clarify if the deletion is irreversible or the exact grace period duration. Overall adequate for a destructive tool.

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?

With 0% schema description coverage, the description must explain all 3 parameters. It only mentions that 'confirm' should be set to 'DELETE', but does not explain 'communityId' or 'customDomainId'. This leaves significant ambiguity for those parameters.

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 clearly states the action is to delete an external custom domain from a managed community, and clarifies that business and community are interchangeable. However, it does not distinguish this tool from sibling tools like 'delete_community_custom_domain' or 'disconnect_custom_domain', leaving ambiguity about when to use which.

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 provides extensive usage guidance: requires confirm=DELETE, check business permissions, FREE businesses cannot use, call check_business_tool_access before inputs, show grace-period warning and resubscribe link, and never proceed when access is blocked. It lacks explicit comparison to alternative tools like disconnect_custom_domain.

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