Pipedrive MCP Server

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

With no annotations provided, the description carries full burden but only mentions filtering capabilities. It lacks critical behavioral details like pagination behavior (implied by 'cursor' parameter but not explained), rate limits, authentication requirements, or whether it's a read-only operation. This leaves significant gaps in understanding how the tool behaves.

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 a single, efficient sentence that front-loads the core purpose and immediately lists key filtering options. Every word serves a purpose with zero wasted text, making it optimally concise while still informative.

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 tool with 19 parameters, no annotations, and no output schema, the description is insufficient. It doesn't address pagination behavior, response format, error conditions, or how to handle the many filtering parameters effectively. The agent would struggle to use this tool correctly without additional context.

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?

The description lists six filtering options (owner, deal, person, organization, type, completion status), which adds some context beyond the schema's 100% coverage. However, it doesn't explain parameter interactions, defaults, or important semantics like how multiple filters combine, so it provides only marginal value over the comprehensive schema descriptions.

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 verb ('List') and resource ('activities from Pipedrive'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'pipedrive_get_activity' (singular fetch) or 'pipedrive_search_deals' (different resource), which prevents a perfect score.

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 implies usage through 'optional filtering' but doesn't explicitly state when to use this tool versus alternatives. For example, it doesn't mention using 'pipedrive_get_activity' for single activities or 'pipedrive_search_deals' for different entities, leaving the guidance incomplete.

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