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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly notes the destructive impact on dependent domains and includes authentication prerequisites, which goes beyond simply saying 'delete.' It does not mention all possible side effects, but the core consequence is disclosed.

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 concise and front-loaded with the core action and impact. The access/auth note is slightly verbose but relevant, and no filler sentences detract from the structure.

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 this is a single-parameter delete operation with no output schema, the description covers the action, the consequence, and the authentication requirement. It could mention how to find the credential ID, but that is a minor gap for a tool this simple.

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?

The schema already fully describes the single parameter: 'DNS credential ID to delete.' The description adds no additional parameter-level meaning, but the 100% schema coverage means the baseline of 3 is appropriate.

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: 'Delete a stored DNS provider credential.' This clearly distinguishes it from siblings like create_dns_credential and list_dns_credentials by calling out both the action and the object.

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 useful context: it warns that domains using this credential will need new credentials for automated verification, which implies this is a consequential action. It does not explicitly name alternatives or when-not-to-use, but the purpose is specific enough that the usage context is clear.

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