Bulk Security Check

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

Annotation readOnlyHint is consistent. Description adds important behavioral details: paid, cost per valid IP, max 1000 IPs, non-billed IPs, and force_refresh semantics.

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?

Description is detailed but well-organized, front-loading purpose then specifics. Slightly verbose but every sentence adds value.

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 no output schema, description explains return format: '{ ip, security } result per valid IP.' Also covers parameters and usage. Adequate for tool complexity.

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%, but description adds extra context: 'fields/excludes use security.* dot paths per item' and 'force_refresh bypasses cache only when the user asks.' Provides more than schema alone.

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 'Read-only bulk security lookup via POST /v3/security-bulk' and distinguishes from sibling tool bulk_lookup_ip by noting when to use which.

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?

Provides explicit guidance: 'Use for security-only batches; use bulk_lookup_ip with include=security when each IP also needs geolocation or other IP domains.' Also explains when to set force_refresh. Could mention when not to use, but alternative is clear.

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