bulk_ioc_lookup

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. Description adds per-type source coverage and that partial failures are visible per indicator, which is useful behavioral context beyond the annotations.

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 concise yet comprehensive, with key information front-loaded: purpose, constraints, source coverage, usage guidance, rate limits, and return structure. No wasted words.

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?

Given the single parameter with full schema coverage, output schema existence, and annotations, the description covers all necessary context: how it differs from the single lookup, rate limits, return structure, and partial failure visibility.

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% with a good description of the 'indicators' parameter. The description adds that auto-detection is per indicator and specifies the maximum of 50, complementing the schema.

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 it batch queries multiple IOCs up to 50 per call, auto-detects type, and queries abuse.ch feeds. It explicitly distinguishes from sibling 'ioc_lookup' for single indicators.

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?

Explicitly says to use for SOC alert triage or batch enrichment, and to use 'ioc_lookup' for single indicators. Also specifies rate limits for Free and Pro tiers.

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