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 states this is an update operation, implying mutation, but doesn't mention whether it's idempotent, what happens with partial updates, if it requires specific permissions, or what the response looks like. For a mutation tool with 17 parameters and no annotation coverage, this leaves significant behavioral gaps.

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 two sentences that directly state the tool's purpose and basic usage. Every word earns its place, and the information is front-loaded with no unnecessary elaboration. It efficiently communicates the core functionality without waste.

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 mutation tool with 17 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address behavioral aspects like error conditions, permission requirements, or response format. While the schema covers parameters well, the description fails to provide the contextual information needed for safe and effective use of this update operation.

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%, with all 17 parameters well-documented in the input schema. The description adds minimal value beyond the schema, only mentioning the required 'deal ID' and 'any fields to update' without providing additional context about parameter interactions or constraints. This meets the baseline for high schema coverage.

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 action ('Update') and resource ('an existing deal in Pipedrive'), making the purpose immediately understandable. It distinguishes from sibling tools like 'pipedrive_create_deal' by specifying 'existing deal' rather than creation. However, it doesn't explicitly differentiate from other update tools like 'pipedrive_update_activity' beyond the resource type.

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 minimal guidance, stating only to 'Specify the deal ID and any fields to update.' It doesn't indicate when to use this tool versus alternatives (e.g., when to update vs. create a deal, or when to use other update tools), nor does it mention prerequisites like authentication or permissions. No explicit exclusions or sibling comparisons are provided.

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