Pipedrive MCP Server

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

No annotations are provided, so the description carries full burden. While it mentions fuzzy matching by default and the ability to use exact match, it doesn't disclose important behavioral aspects like pagination, rate limits, authentication requirements, error handling, or what the response format looks like. This is inadequate for a search tool with no annotation coverage.

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?

The description is extremely concise with just one sentence that efficiently communicates the core functionality. Every word earns its place, and the information is front-loaded with no unnecessary elaboration.

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?

Given no annotations and no output schema, the description is incomplete for a search tool with 6 parameters. It doesn't explain what the tool returns, how results are structured, whether there's pagination, or any error conditions. For a tool that likely returns complex deal data, this leaves significant gaps for the agent.

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 6 parameters thoroughly. The description adds minimal value by mentioning fuzzy matching (implied by the exact_match parameter) but doesn't provide additional context about parameter interactions, search behavior, or result ordering beyond what's in the schema.

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 clearly states the tool searches for deals by text in title with fuzzy matching, providing a specific verb (search) and resource (deals). However, it doesn't explicitly distinguish this from sibling tools like pipedrive_list_deals or pipedrive_get_deal, which could cause confusion about when to use each.

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 provides no guidance on when to use this tool versus alternatives. With multiple sibling tools for accessing deals (list_deals, get_deal, search_deals), the agent receives no help in selecting the appropriate tool for different scenarios like listing all deals versus searching by text.

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