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

The readOnlyHint annotation already establishes this is a safe, non-mutating read. The description adds the REST endpoint reference but says nothing about pagination behavior, result ordering, or how the cursor interacts with limit — details that matter for a search endpoint with 500-result caps.

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 short sentences, zero filler, with the core action front-loaded and the endpoint detail secondary. Nothing is wasted and nothing important is buried.

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?

With 8 parameters, no output schema, and only a readOnlyHint annotation, the description is thin. The schema carries all parameter detail, but there is no guidance on pagination flow, result shape, or how search differs from listing — leaving the definition minimally adequate rather than complete.

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 every parameter (term, limit, cursor, fields, status, person_id, exact_match, organization_id) is already documented in the schema. The single sentence 'across selected fields' loosely gestures at the fields parameter but adds no meaning beyond what the schema provides. 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 and resource ('Search deals by term across selected fields') and even names the underlying REST endpoint. It is clear what the tool does, but it never contrasts itself with the obvious siblings pipedrive_list_deals or pipedrive_search_items, so an agent must infer the distinction.

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 description gives no when-to-use guidance, no exclusions, and no mention of alternatives such as pipedrive_list_deals (browse) or pipedrive_search_items (cross-entity search). The agent is left to infer that this is for term-based deal lookup.

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