domain_whois

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

With no annotations, the description should fully disclose behavioral traits. It only indicates a query (implied read-only) but does not mention potential failure cases, authentication needs, rate limits, or data freshness. The pricing note is tangential to behavior.

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 extremely short, which can be considered concise, but it lacks structure and substance. It does not earn its place beyond identifying the tool and providing pricing info, missing opportunities for helpful context.

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 no output schema, the description should explain what the tool returns. It only says 'WHOIS query', offering no details on the response format or content. The description is incomplete for an agent to understand the tool's full capabilities.

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 one parameter (domain). The description adds no extra meaning beyond the schema's '域名'. The baseline of 3 is appropriate since the schema already describes the parameter adequately.

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 'WHOIS域名查询' (WHOIS domain query) and the tool name itself is domain_whois, making the purpose clear. However, it lacks specification of what details are returned (e.g., registrar, expiry date), which would enhance differentiation from siblings like ens_resolve.

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 is provided on when to use this tool vs alternatives. The description does not mention prerequisites, context, or exclusions. The agent receives no help in deciding between domain_whois and other lookup tools.

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