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

With no annotations, the description carries full burden and delivers: 'Preserves all other records' (non-destructive behavior), a domain constraint, and a token cost. It does not describe failure modes or irreversibility, but covers key safety traits.

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?

Three concise sentences, front-loaded with the primary action. No wasted words; each sentence carries useful information (action, safety, prerequisite, cost).

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 tool with full schema coverage and an output schema, the description covers the essential context: what it does, how to obtain host_id, the Namecheap requirement, token cost, and preservation guarantee. It is complete for agent selection and invocation.

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 baseline is 3. The description reinforces the host_id source ('Get host_id from domains.get_dns_hosts') and adds the Namecheap constraint, but adds no new parameter-level syntax or format beyond 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 opens with a specific verb ('Remove'), the exact resource ('DNS host record'), and the scope ('from a managed domain by host_id'). This clearly distinguishes it from sibling tools like domains.add_dns_host and domains.get_dns_hosts.

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 clear context on prerequisites: 'Get host_id from domains.get_dns_hosts' and 'The domain must use Namecheap DNS.' It does not explicitly mention alternatives or when not to use, but the workflow is unambiguous.

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