range_statsPer source: prefix counts, total addresses and /24-equivalents, smallest and largest prefix, the publishing URL and when it was last fetched; plus prefixes published by more than one operator. This is the sizing and freshness information an allowlist decision needs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description goes beyond annotations by revealing what data is returned, including freshness information and multi-operator overlap, which helps the agent understand the tool's output behavior. It does not mention pagination or exact response formatting, but for a zero-parameter read-only stats tool that is a minor gap.
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 compact and front-loaded with concrete output details, followed by a single sentence explaining its practical relevance. Every sentence earns its place, and there is no wasted wording.
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 tool with no parameters, no output schema, and strong safety annotations, the description provides enough detail about the returned information and the decision context in which it is useful. An agent can understand what this tool offers and why it might be selected.
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 tool has zero parameters and the input schema is empty, so there are no parameter semantics to clarify. The description appropriately focuses on what the tool reports rather than on inputs, matching the baseline for a parameterless tool.
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 identifies what the tool provides: per-source prefix counts, addresses, /24-equivalents, smallest/largest prefix, publishing URL, and last-fetch time, plus multi-operator prefixes. It is distinct from siblings like lookup_prefix or verify_batch, but it lacks an explicit action verb such as 'returns' or 'computes'.
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 closing sentence gives practical usage context: this is the sizing and freshness information an allowlist decision needs. It implies when to use the tool, though it does not explicitly contrast it with sibling tools or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation: CIDR overlap lookup, source statistics, verification-method metadata, batch address verification, and ACL export. lookup_prefix and verify_batch both touch prefix matching, but their input types and intended use cases are clearly separated.
Most names follow a clear snake_case verb_noun pattern like export_ip_acl, lookup_prefix, and verify_batch. range_stats and verification_methods are noun phrases rather than verb-led names, creating a minor but readable inconsistency.
Five tools is well-scoped for a focused IP-verification service. Each tool earns its place and covers a distinct part of the workflow without unnecessary sprawl or redundancy.
The set covers address verification, prefix overlap analysis, source freshness and sizing, verification-method lookup, and configuration export. There are no obvious missing operations that would prevent an agent from completing the core crawler-IP verification workflow.