Bulk verify international addresses

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

The description adds no behavioral context beyond annotations. Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description does not clarify verification behavior (e.g., result format, error handling). With annotations present, the bar is lower, but no added value.

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?

A single sentence that front-loads key information: bulk, up to 1,000, non-US addresses. No unnecessary 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?

No output schema is present, and the description does not mention return values, error handling, or detailed behavior. The nested addresses parameter is complex but only partially documented. The tool is incomplete in providing context for an AI agent to use 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?

Schema coverage is 50%, and the description does not explain parameter meaning beyond what the schema provides. The 'extra' parameter is mentioned in schema but not in description. The description does not compensate for undocumented fields like secondary_line or city.

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 verifies non-US addresses in bulk (up to 1,000), distinguishing it from single international verification (lob_intl_verifications_create) and US bulk verification (lob_bulk_us_verifications_create). The verb 'verify' and resource 'bulk international addresses' are specific.

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 implies bulk use vs single but does not explicitly state when to use this tool versus alternatives like lob_intl_verifications_create or lob_bulk_us_verifications_create. No mention of when not to use or prerequisites.

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