update_whois_contact

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

With no annotations, the description must disclose behavioral traits. It only states 'Update', implying mutation, but does not mention whether the contact is entirely overwritten, if verification is triggered, or if special permissions are needed.

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 very concise (4 words), but this brevity sacrifices completeness. While not verbose, it could be expanded with critical context without becoming overly long.

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 tool's complexity (3 params, nested object, no annotations, no output schema), the description is insufficient. It fails to explain return values, side effects, or typical use cases.

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 low (33%), with the domain parameter lacking a description. The tool description does not add meaning beyond the schema; it omits explaining the domain format or the effect of the provider parameter.

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?

Description 'Update domain WHOIS contact' clearly specifies the verb 'Update' and the resource 'domain WHOIS contact'. It distinguishes the tool from siblings like get_whois_contact (read), and other domain management tools (create, delete, register).

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?

No guidance on when to use this tool versus alternatives, prerequisites (e.g., domain must be registered), or when not to use (e.g., for transfers). The description provides no usage context.

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