delete_dns_access_list

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds the explicit warning 'This is irreversible,' which reinforces the destructive nature with a stronger claim. However, it does not mention the confirm safety gate or dry_run preview, though these are documented in the schema.

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 extremely succinct: one declarative sentence plus a brief warning. Every word earns its place, and the warning is front-loaded to alert the agent to the tool's destructive nature.

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?

The tool has a complete schema, output schema, and destructive annotations, so the description does not need to explain return values or basic safety. However, it omits any mention of the typical workflow, such as whether apply_dns_resolver_changes must follow deletion to make changes effective, which is a notable gap given the sibling context.

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 description coverage is 100%, so the input schema fully explains all four parameters including confirm, dry_run, and apply_immediately. The description itself adds no additional parameter context, so it does not exceed the baseline provided by the schema.

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 verb 'Delete' and the resource 'DNS Resolver access list', making the tool's purpose unambiguous. It distinguishes itself from sibling tools like create_dns_access_list, update_dns_access_list, and apply_dns_resolver_changes by specifying the destructive action.

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 implicitly conveys that this tool is for deleting an access list, but it gives no explicit guidance on when to use it versus alternatives. It does not mention that one should use search_dns_access_lists to find the correct access_list_id, nor does it indicate whether apply_dns_resolver_changes is needed after deletion.

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