domains_deleteWHOISProfileV1

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

With no annotations provided, the description must fully disclose behavioral traits. It notes that profiles should be 'unused', but it does not describe consequences of deleting a used profile, whether deletion is reversible, or any prerequisites (e.g., ownership). This is insufficient for a delete operation.

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 two sentences long and contains only essential information. No redundant or filler text.

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?

Given the simplicity of the tool (one param, no output schema), the description provides the basic purpose and usage hint. However, it lacks details on how to determine if a profile is unused, what happens after deletion, and error handling, which would help an agent invoke it correctly.

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 describes the single parameter 'whoisId' as 'WHOIS ID'. The tool description adds no additional meaning beyond that. Since schema description coverage is 100%, baseline is 3.

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 tool's action: 'Delete WHOIS contact profile.' It uses a specific verb (Delete) and resource (WHOIS contact profile), and it is distinct from sibling tools like create, get, list, and usage tools.

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: 'Use this endpoint to remove unused contact profiles from account.' This provides clear context, but it does not specify when not to use it or mention alternatives, which is acceptable given the tool's specificity.

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