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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description goes beyond them by naming the concrete API endpoint and the return envelope ({ meta, response }), which is genuinely useful since no output schema exists. It stops short of describing pagination behavior or rate limits.

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?

Three short, front-loaded sentences with the core purpose first. The enumerated parameter list is largely redundant given the schema's 100% coverage, which is the only wasted content.

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 paginated read-only list tool with a fully described schema, the description supplies the endpoint and the { meta, response } return shape, which compensates for the missing output schema. Nothing essential for a correct call is missing, though pagination defaults are left to the schema.

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 page/limit/fields/search/filters are already fully documented in the schema with examples and defaults. The description only re-lists the parameter names (_page/_limit/_fields/_filters/_search) without adding syntax or format detail, so the baseline 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?

States a specific verb+resource and defines the resource semantically ('sales opportunities in the pipeline'), which is more than a restatement of the name. It does not, however, distinguish itself from sibling get_prospect (single) or explain how it relates to list_jobs/list_companies, so sibling differentiation is absent.

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 listing/plural framing implies 'use this to enumerate prospects', and the exposed filter/search params hint at retrieval use cases, but there is no explicit when-to-use, no when-not-to-use, and no reference to get_prospect for single-record lookups. Usage is inferable but not stated.

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