combell_dns_records_delete

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

Annotations already mark this as destructive and non-idempotent, and the description adds valuable context beyond that: the operation is irreversible and changes live DNS. This explicitly warns the agent about real-world impact, which is genuinely useful behavioral information.

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, direct sentence followed by a compact side-effect warning. It is front-loaded with the action and resource, contains no filler, and every word adds meaning.

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 two-parameter delete operation with no output schema, the description covers the essential context: what is deleted, from where, and the irreversible live-DNS consequence. The only minor omission is an explicit note about response behavior, but that is not critical for this type of destructive tool.

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 documents record_id as 'The record id to delete,' but domain_name has no description in the schema. The tool description only says 'from a domain,' which indirectly clarifies that domain_name is the domain whose record should be deleted, but it does not fully compensate for the 50% schema coverage gap.

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 uses a specific verb ('Delete') and a clear resource ('a DNS record from a domain'), which precisely distinguishes this from sibling tools like combell_dns_records_create, update, list, and get. The side-effect warning also reinforces that this is the destructive removal operation.

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 clearly implies the tool is used when you need to remove a DNS record from a domain, but it does not explicitly state when to use it over alternatives such as combell_dns_records_create or combell_dns_records_update. The context is unambiguous, but no exclusions or alternative routing are provided.

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