Delete WHOIS profile

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

Annotations already mark this as destructive and idempotent, so the description only needs to add context beyond those flags. It adds 'unused' and 'from account' context but does not disclose side effects, restrictions, or behavior on failure. No contradiction with annotations.

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?

Two short sentences, front-loaded with the action, and no filler. Every sentence contributes either the operation or the intended use case.

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 one-parameter delete operation with strong annotations, this is nearly complete: action, target, parameter, and intended use are all present. It could be slightly richer by noting that the profile should not be in use or default, but 'unused' already implies the key constraint.

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% and the single whoisId parameter is already described as 'WHOIS ID'. The description adds no parameter-level detail, but none is required given the schema's complete coverage.

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 'Delete WHOIS contact profile,' a specific verb plus resource, and the second sentence reinforces the exact operation ('remove unused contact profiles from account'). This unambiguously separates it from the get/create/change/set-default siblings.

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?

'Use this endpoint to remove unused contact profiles from account' gives a clear condition for when to call it. It does not explicitly name alternatives or exclusions (e.g., don't delete a profile in use/default), so it stops short of a 5.

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