DNS_deleteDNSRecordsV1

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

No annotations provided, so description carries full burden. It indicates deletion is destructive but does not mention prerequisites, irreversibility, or required permissions, and the filter discrepancy adds uncertainty.

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?

Description is relatively concise with clear first sentence, but the misleading filter information wastes some words and could be restructured to match schema.

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 delete-tool with filtering, the description is incomplete because it does not specify how to provide the filter parameters (name/type) given the schema only includes 'domain', and lacks any output schema details.

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?

Input schema has only 'domain' with minimal description; the description adds filter semantics (name/type) that are not present in the schema, creating a contradiction and failing to add useful parameter meaning.

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 tool deletes DNS records for a domain, but mentions filtering by name/type which are not in the input schema, causing confusion and reducing clarity.

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?

Provides guidance on when to use 'Update zone records' for partial deletions of records with same name/type, but the missing filter parameters in schema make the guidance unactionable.

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