find_and_verify_corporate_emails

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the MX fingerprinting mechanism (Google Workspace, Microsoft 365, Proofpoint, Mimecast), which is valuable context, but says nothing about error handling, rate limits, verification depth, or side effects.

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, front-loaded sentence with no filler. It is dense but efficiently readable, and every clause 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?

With no output schema and no annotations, the description leaves what the tool actually returns unspecified (email addresses? verification status? confidence?). For a tool that resolves and verifies data, the lack of return-value context is a notable gap.

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 all three parameters are fully documented in the schema itself. The description only broadly maps to those inputs ('prospect names and company domains') and adds no syntax or format details beyond what the schema already states.

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?

States a specific verb and resource: 'Resolve and verify B2B corporate email addresses.' The added detail of MX provider fingerprinting distinguishes it from generic enrichment tools, though it doesn't explicitly name a sibling alternative for comparison.

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 B2B prospecting scenario is implied ('from prospect names and company domains'), but there is no explicit when-to-use, when-not-to-use, or routing guidance relative to siblings like score_email_deliverability_risk or enrich_company_websites.

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