Bgp Ip

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds no behavioral details beyond the action itself, such as rate limits, result scope, or data source assumptions. It does not contradict annotations, but also does not enrich behavioral understanding beyond what structured data already supplies.

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 a single, front-loaded sentence with zero extraneous words. It directly states the action and resource, making it highly concise while still communicating the core function.

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?

For a simple single-parameter tool with an output schema and rich annotations, the description is minimally adequate. It tells the agent what to input and what general kind of result to expect, but it leaves out any caveats, data scope, or relationship to sibling tools, making it complete only in a basic sense.

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?

With 0% schema description coverage, the description partially compensates by indicating the 'ip' parameter is the IP address for a routing lookup. However, it does not specify formats (IPv4/IPv6), constraints, or whether CIDR is accepted, and the parameter name already strongly suggests an IP address.

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 uses a specific verb ('lookup') and resource ('IP to prefix/ASN routing'), clearly identifying what the tool does. It does not explicitly differentiate from sibling tools like whois_ip or bgp_asn, but it is unambiguous in its own meaning.

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 about when to use this tool versus siblings such as bgp_asn, whois_ip, or geoip. The description does not mention scenarios, prerequisites, or alternatives, leaving the agent without decision support.

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