domains_deleteWHOISProfileV1

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

No annotations are provided, so the description must disclose behavioral traits. It states the action and a precondition (profile must be unused) but does not mention that deletion is irreversible, any required permissions, or side effects. With the delete operation, such information is critical.

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: the first states the action, the second gives usage guidance. No unnecessary words or filler.

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 one parameter and no output schema, the description is adequate but incomplete. It could mention irreversibility, the need to check usage beforehand (e.g., referencing domains_getWHOISProfileUsageV1), and what the response indicates.

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 coverage is 100% with the parameter 'whoisId' described as 'WHOIS ID'. The tool description adds no extra meaning beyond the schema, so the 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 verb 'Delete' and the resource 'WHOIS contact profile', distinguishing it from siblings like domains_createWHOISProfileV1 and domains_getWHOISProfileV1. The phrase 'remove unused contact profiles' adds specific context about the precondition.

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 indicates when to use the tool (to delete unused profiles) but does not explicitly state when not to use it (e.g., if the profile is in use) or suggest alternatives like domains_getWHOISProfileUsageV1 to check usage first.

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