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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds only that email verification status appears in results; it says nothing about required project/site scoping, pagination defaults, or the several filtering dimensions the tool supports — context an agent would need to use it effectively.

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 efficient, though its brevity borders on under-specification given the tool's 9 parameters.

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 9-parameter, zero-coverage listing tool with no output schema, one sentence is far from complete — required scoping IDs, pagination limits (perPage max 100), and the status/verification enum filters all go unmentioned. The description alone cannot support correct invocation.

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 must compensate and does not: projectId, siteId, page, perPage, search, sortBy, sortOrder, statuses, and verificationStatuses are all undocumented. Only a faint gesture toward verification status hints at the verificationStatuses filter.

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 names one returned attribute (email verification status). However, it does not distinguish this from close siblings like list_prospects, list_leads, or list_outreach_threads — "people found for outreach" could describe any of them, so an agent cannot route confidently without guessing.

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 when-to-use, when-not-to-use, or alternative tools are named despite several plausible overlaps (list_prospects, list_leads). The agent is left to infer that this tool returns contact records scoped to a project/site.

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