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

The readOnlyHint annotation already establishes this is a safe read, so the bar is lower. The description adds only the REST mapping (GET /api/v2/itemSearch), which is largely redundant with the annotation, and discloses nothing about rate limits, result caps, or how pagination via next_cursor behaves across mixed item types.

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, front-loaded with the capability and with no filler. The trailing REST endpoint reference earns its place only for debugging purposes and is the one element that does not help an agent select or call the 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?

With seven parameters, a read-only annotation, and no output schema, the description is adequate but thin: it never hints at the shape of the response or how the opaque cursor relates to the returned results, and it does not explain interactions between fields, item_types, and exact_match.

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% — term length, limit bounds/default, cursor provenance, allowed item_types, and exact_match/search_for_related_items semantics are all documented in the schema. The description adds no parameter-level meaning beyond that, 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 (search) and an explicit scope (global, across deals, persons, organizations, products, leads, files). The word 'global' plus the enumerated item types cleanly distinguishes it from the entity-scoped siblings pipedrive_search_deals, pipedrive_search_persons, and pipedrive_search_organizations.

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?

Usage is implied rather than stated: 'global search across multiple item types' suggests this is the tool for cross-type lookups, leaving the entity-specific search siblings as the alternative. However, it never says when to prefer this over pipedrive_search_deals or what happens if item_types is omitted, so the agent must infer the routing.

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