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

With no annotations, the description carries full burden and does so: 20-indicator cap, the critical caveat that found:false means 'not recorded', not 'safe', the conditional free-batch behavior, and the full payment path (x402 via params._meta and PAYMENT-SIGNATURE header, or Gumroad X-API-KEY). This is material behavior an agent cannot infer from the schema.

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?

Front-loaded with purpose before routing and behavior; the labeled sections (SIBLING DIFFERENTIATION, BEHAVIOR) aid scanning. Somewhat dense with ALL-CAPS labels and payment detail that could be marginally tighter, but no sentence is filler.

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?

No output schema exists, yet the description covers return parity with get_ioc_context (same aggregated provenance), the batch semantics of found:false, capacity limits, and the payment/quota model. An agent has everything needed to call and interpret this tool.

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% and the single required 'values' parameter is already documented in the schema including the max-20 limit. The description's mention of 'up to 20 indicators per call' largely restates the schema rather than adding format or per-element semantics (e.g. mixed-type batches, normalization rules).

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?

States a specific verb (looks up) and resource (multiple indicators) with the exact accepted types (IPs, domains, URLs, hashes) and framing (batched pre-action safety check). It explicitly separates itself from get_ioc_context (single indicator) and get_threat_indicators (bulk feed sync).

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?

Gives explicit when-to-use ('checking several indicators at once, e.g. all URLs an agent is about to visit'), when-not-to-use ('Do NOT use for a single indicator', 'or bulk feed synchronization'), and names the replacement sibling for each case. Nothing is left to inference.

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