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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety and mutation behavior are covered. The description adds only 'GET /people', which is mildly useful, and says nothing about pagination limits, rate limits, or the shape of results beyond the field list. With annotations carrying the safety profile, this modest addition merits a 3.

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 front-loaded sentences with essentially no waste: the resource and fields come first, the search-vs-filter hint second, the endpoint last. The one minor redundancy is re-listing fields that the schema already names.

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 16-parameter read-only list with a fully documented schema and no output schema, the description need not explain return values. It covers purpose, filtering, and the endpoint adequately; the only gap is the absence of pagination/next_page guidance, which the schema supplies at the parameter level.

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 the schema already documents every parameter's matching semantics and defaults. The description's mention of the searchable fields (name, email, company name) and filterable attributes duplicates rather than extends the schema, 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 ('List or search') and resource ('people (leads and contacts)'), and enumerates the salient fields available (email, phones, position, company, owner, lead status, tags). It is clearly distinguishable from siblings like pipelinecrm_list_companies and pipelinecrm_list_deals, and even from the narrower pipelinecrm_list_company_people.

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 sentence 'Use search for a quick match... or filter precisely' gives useful conditional guidance, but only about how to use the parameters, not when to select this tool over alternatives. It never says when to prefer pipelinecrm_get_person for a single known record or when to use the list_company_people variant, so routing guidance is implied rather than explicit.

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