postgrid_verify_addresses_batch

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully reveals the 2,000-address cap, the 500-address batching behavior, and that a verification status is returned per address. However, it does not mention partial failure behavior, error semantics, or whether batching is transparent to the caller, which are relevant for a batch operation.

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?

Two sentences with no filler. The core operation is front-loaded, followed by the key constraint and the expected output. Every sentence earns its place.

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?

For a one-parameter batch tool with no output schema, the description adequately covers input, limits, chunking, and the per-item return value. The main gap is the absence of a more precise response structure or failure semantics, but the description is sufficient for an agent to make a correct first call.

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 description coverage is 100%, so the schema already documents the addresses array and its nested fields. The description adds the batching detail, but that is behavioral context rather than additional parameter meaning. Per the baseline rule, the score stays at 3.

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 uses a specific verb and resource ('Verify multiple addresses') and immediately differentiates itself from the singular sibling postgrid_verify_address by emphasizing batch processing. It is clear about the operation's scope without requiring the agent to inspect the schema.

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 phrase 'Verify multiple addresses at once' provides clear context for when to use this batch tool versus a single-address verification tool. It does not explicitly name alternatives or state when not to use it, so it stops short of full exclusion guidance.

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