network_asn_lookup

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

With no annotations provided, the description bears full burden. It states the basic behavior but omits response format, rate limits, authentication needs, or side effects. The mention of worker_id hints at distributed processing but lacks detail.

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 sentences, but includes redundant 'Menu ID: asn_lookup' and defers to describe_tool. Could be more concise by removing the menu ID and integrating key info directly.

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?

Adequate for a simple lookup tool with one optional parameter and no output schema. The description covers core purpose but leaves detailed guidance to describe_tool, which may be acceptable if that tool provides completeness.

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% for the single parameter worker_id, and the description adds minimal context (optional, default behavior). Baseline 3 is appropriate since schema already documents well.

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 performs ASN lookups to find network ownership, ISP information, and routing details for any IP address or domain. This specific verb+resource combination distinguishes it from sibling network 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?

No guidance on when to use this tool versus alternatives like network_whois or network_bgp_route_lookup. Only a reference to describe_tool for more info, but no explicit conditions or exclusions.

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