Pipedrive MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: the person is 'marked as deleted' (indicating a soft delete) and 'permanently removed after 30 days' (specifying a delayed hard deletion). This adds valuable context beyond the basic action, though it could mention permissions or error handling.

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 and front-loaded, consisting of two sentences that directly state the action and a critical behavioral detail. Every sentence earns its place by providing essential information without any wasted words or redundancy.

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 the tool's complexity (a destructive operation with delayed permanent deletion), no annotations, and no output schema, the description is reasonably complete. It covers the core behavior and timing, but could be enhanced by mentioning return values or error conditions to fully guide an agent in handling responses.

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 input schema has 100% description coverage, with the 'id' parameter clearly documented as 'Person ID to delete'. The description does not add any additional meaning or details about the parameter beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without extra value.

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 specific action ('Delete a person') and distinguishes it from sibling tools like pipedrive_get_person or pipedrive_update_person by focusing on deletion rather than retrieval or modification. It specifies the resource ('person') and the verb ('delete') unambiguously.

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 when deletion of a person is needed, but does not explicitly state when to use this tool versus alternatives (e.g., vs. pipedrive_update_person for soft deletes or other deletion tools). It mentions the 30-day permanent removal, which provides some context but lacks explicit guidance on prerequisites or exclusions.

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