delete_dns_credential

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

With no annotations, the description carries the burden of behavioral disclosure. It explicitly states the downstream impact: 'Domains using this credential will need new credentials for automated verification.' It also explains the session/authentication requirement, giving the agent important preconditions beyond the basic delete action.

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: it opens with the action, then gives the key consequence, then the access requirements. Every sentence adds necessary value with no redundancy or filler.

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 one-parameter destructive tool with no output schema, the description covers the core action, the side effect on domains, and the access prerequisite. It could mention how to locate the credential ID (e.g., via list_dns_credentials), but this is a minor gap for an otherwise complete description.

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 input schema already fully documents the single required 'id' parameter with the description 'DNS credential ID to delete' (100% schema description coverage). The tool description does not add additional meaning beyond what the schema provides, so 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 the specific verb and resource: 'Delete a stored DNS provider credential.' It clearly distinguishes this from sibling tools like create_dns_credential and list_dns_credentials by its destructive, deletion-focused purpose.

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 clear context for when the tool is applicable: removing a stored DNS credential that is no longer needed. It also gives explicit access prerequisites via PROOF_API_KEY or start_login. It does not explicitly name alternative tools or exclusions, but the destructive action and consequence make the usage context clear.

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