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

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world, so the safety profile is covered. The description adds only that results carry email verification status; it says nothing about pagination defaults, filtering behavior, or the enumeration values that constrain results.

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 tight sentence with no filler, front-loading the resource. It is efficient but arguably too terse for a 9-parameter tool.

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 nine-parameter, two-enum, zero-coverage-schema list tool with no output schema, the description leaves pagination, filtering, sorting, and required identifiers entirely unexplained. It is not sufficient for an agent to call the tool confidently beyond the trivial case.

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 0% across 9 parameters, so the description is the only prose source and it explains just one concept (verification status) out of many. It gives no meaning for page/perPage pagination, search, statuses, sortBy, or the required projectId/siteId scoping.

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 ('List the people found for outreach') and adds the notable scope detail of email verification status. It is distinguishable from similar siblings like list_prospects and find_prospect_contact, though it does not name them explicitly.

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?

No guidance on when to use this versus list_prospects, list_leads, or find_prospect_contact, and no mention of prerequisites such as needing a project and site. The agent must infer usage entirely from the name and required params.

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