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 adds the REST endpoint mapping (GET /api/v2/organizations/search) and the fact that the search spans 'selected fields', which is mild extra context. It does not disclose pagination behavior beyond the cursor parameter, nor which fields are searched by default.

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 purpose and followed by the endpoint reference. No filler, no redundancy, and the key scoping fact appears first.

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 five-parameter read-only search tool with no output schema, the definition plus the fully documented schema covers what an agent needs to call it correctly. The remaining gap is behavioral: no mention of default searched fields or how cursor pagination terminates, which would help for multi-page retrieval.

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 all five parameters with constraints, defaults, allowed field values, and cursor semantics. The phrase 'across selected fields' loosely points at the 'fields' parameter but adds no detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

The description gives a specific verb+resource ('Search organizations by term') and clarifies scope ('across selected fields'), which distinguishes it from pipedrive_get_organization and pipedrive_list_organizations. It never names the sibling search tools (pipedrive_search_persons, pipedrive_search_deals, pipedrive_search_items), so differentiation relies on the reader inferring it from the entity name.

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?

There is no explicit when-to-use context, no statement of when to prefer this over pipedrive_list_organizations or the generic pipedrive_search_items, and no prerequisites. The only implied guidance is the presence of a 'term' parameter, which the agent could already read from the schema.

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