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

Annotations already declare readOnly, idempotent, and non-destructive behavior, and the description adds meaningful context: it returns the matching prefix, source, mirror timestamp, and operator rollup. It also discloses the important semantic that a miss is not evidence of a fake, and notes the same implementation is callable via plain HTTP.

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?

Most sentences earn their place, but the opening 'FIRST CALL, needs nothing: whoami' is an unrelated directive that adds confusion and does not describe verify_batch itself. The description is packed with useful detail, but the extraneous preamble and the non-MCP URL make it less tight than it should be.

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?

With one parameter, no output schema, and straightforward complexity, the description is complete: it explains input formats, maximum size, return contents, an example, claim semantics, and edge-case caveat. An agent has enough information to invoke the tool correctly.

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 schema already documents the single 'addresses' parameter thoroughly, including accepted formats and the 500 maximum, so the baseline is 3. The description adds value by explaining {ip, claim} pairs and providing a concrete example showing how claims are matched or missed.

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 states a specific verb and resource: 'Check up to 500 addresses against every mirrored operator prefix list in one call.' It clearly communicates the batch nature, the scope over all mirrored lists, and what is returned. The example reinforces the purpose and distinguishes it from single-address siblings like verify_my_address.

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 gives clear context for when to use the tool: batch verification of up to 500 addresses or {ip, claim} pairs. It does not explicitly name alternatives or state when not to use it, but 'in one call' and the 500-address limit signal the intended use case.

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