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

With no annotations, the description carries the full burden. It usefully discloses a billing trait ('only verified emails are billed') and the alternate inputs, but says nothing about cost per lookup, rate limits, failure/no-match behavior, or whether unverified emails are returned. Partial disclosure for a tool with zero annotation coverage.

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 tight sentences: the core action leads, the input strategy follows, and the billing note closes. Every clause earns its place with no filler.

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 covers the action, inputs, and billing cue, but with no annotations and no output schema it leaves return shape, no-match handling, and cost behavior unspecified. Reasonable but thin for a billing-sensitive lookup tool.

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?

Reported schema coverage is 0%, but the single parameter is an array of person objects; the description clarifies that either a company domain or a company name can be used to resolve the email, adding real meaning. It says nothing about the array limits (maxItems 2000), the required first_name, or last_name behavior, so it only partly compensates for the coverage gap.

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+resource ('finds the verified work email of people') and the inputs it consumes (name plus company domain or company name). It implicitly distinguishes itself from siblings like verify_emails, though it never names an alternative. Clear purpose, but no explicit sibling differentiation.

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?

Usage is implied by the input description ('from their name and company domain (or company name)'), which tells the agent what to supply. However, there is no statement of when to prefer this over verify_emails, find_people_at_companies, or find_linkedin_leads, and no exclusions or prerequisites.

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