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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's real value is the downstream consequence: domains relying on this credential lose automated verification. It also discloses the authentication prerequisite and the fact that a session is opened by this tool. Missing only whether deletion is reversible/undoable and behavior on a nonexistent ID.

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?

Purpose and consequence are front-loaded in two short sentences, with authentication facts separated into an ACCESS block. The auth text is somewhat boilerplate-heavy but is clearly delineated rather than mixed into the core description.

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?

An output schema exists, so return values need not be explained. The definition covers what is deleted, the side effect on domain verification, and the auth requirement — everything an agent needs before invoking a destructive one-parameter 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?

Schema coverage is 100% and the single parameter already carries the description 'DNS credential ID to delete'. The tool description adds no format, source, or validation detail beyond that, so it merely matches the baseline for high-coverage schemas.

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?

Names a specific verb+resource ('Delete a stored DNS provider credential'), which is unambiguous against siblings like create_dns_credential and list_dns_credentials. It does not explicitly name an alternative tool, but the operation is distinct enough that no disambiguation is needed.

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 second sentence implies a caution condition — domains using this credential will need new credentials for verification — which functions as a when-to-be-careful signal. However, there is no explicit guidance on prerequisites (e.g., checking affected domains first with check_domain_credentials, or listing IDs via list_dns_credentials) and no stated when-not-to-use.

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