sophos_dns_delete_custom_domain

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

The description lacks behavioral details beyond the fact that it deletes. With no annotations, the agent is left uninformed about idempotency, error handling, reversibility, or side effects. For a delete operation, more clarity on behavior is needed.

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 a single focused sentence without unnecessary words. It is concise and front-loaded, but could be slightly expanded to include more context without becoming verbose.

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 delete tool with two well-described parameters and no output schema, the description is minimally adequate. However, it does not reference the DNS context or differentiate from sibling DNS tools, leaving some room for improvement.

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 provides clear descriptions for both parameters ('Tenant UUID' and 'Custom domain list UUID to delete'), achieving 100% coverage. The description adds no further parameter context, so baseline score 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 clearly states the action (delete) and the resource (custom domain list), distinguishing it from other delete operations on different resources (e.g., locations, policies). However, it is essentially restating the tool name with minimal additional information.

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?

No guidance is provided on when to use this tool versus alternatives like sophos_dns_delete_location or sophos_dns_delete_policy. There is no mention of prerequisites, conditions for deletion, or any context about when deletion is appropriate.

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