WHOIS ASN Lookup

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

Annotations indicate read-only, non-destructive, idempotent, and open-world hints. The description adds a critical warning about large responses and token consumption, and mentions returning raw WHOIS text, providing behavioral context beyond the 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?

The description is concise (two sentences plus a warning), front-loaded with the core purpose and return values, and every sentence adds value. No extraneous words.

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 a simple single-parameter tool, the description covers the purpose, input format, return fields, and a crucial warning about large responses. No output schema exists, but the listed return fields suffice.

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 single parameter 'asn' has 100% schema coverage, but the description adds semantic value by explaining it accepts with or without the 'AS' prefix, which is not explicit in the schema property description.

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 retrieves real-time WHOIS data for an ASN, listing specific return fields (AS name, organization, etc.). It distinguishes from sibling tools like whois_domain_lookup by focusing on ASN-specific data.

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 implies usage for WHOIS ASN queries but does not explicitly state when not to use this tool or mention alternatives. The warning about large ASNs provides some guidance on usage constraints but no exclusions.

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