verify_emails_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 disclosure. It does state that it returns verification status and confidence score for each email, which is useful. However, it does not explicitly disclose whether the operation is read-only, any side effects, authentication requirements, or rate limits. The absence of this information leaves gaps, though the basic behavior is communicated.

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 two sentences, front-loaded with the main purpose. Every sentence adds value: the first states what it does, the second describes output and use case. No fluff or redundancy.

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?

The description is complete for a simple tool with one parameter and no output schema. It covers the action, limit, return value, and a use case. It does not mention error handling or behavior on invalid emails, but this is a minor gap given the simplicity and schema enforcement.

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?

The schema has 100% coverage with the only parameter 'emails' described as 'Email addresses to verify (max 25).' The description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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 the tool verifies multiple email addresses in a single batch, with a specific max limit of 25. It distinguishes itself from the singular sibling verify_email by emphasizing batch processing. The verb 'verify' plus specific scope makes the purpose unambiguous.

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 provides clear context for when to use the tool: 'Efficient for cleaning outreach lists.' This suggests a batch use case. However, it does not explicitly mention alternatives like verify_email for single checks or state when not to use this tool, so it falls short of a 5 but is above a 3 due to the clear usage context.

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