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 mentions 'mark activities as done' as a key behavior, which is useful context beyond the basic update action. However, it lacks critical information such as whether this is a destructive operation (e.g., overwrites existing data), what permissions are required, error handling, or response format. For a mutation tool with zero annotation coverage, this leaves significant 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, both of which earn their place: the first states the core action, and the second provides a key usage example. There is no wasted language, and it is front-loaded with the essential information. This is an excellent example of efficient communication.

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 complexity (19 parameters, mutation operation) and lack of annotations and output schema, the description is insufficiently complete. It doesn't cover behavioral aspects like side effects, error conditions, or response expectations. While concise, it fails to provide the depth needed for an agent to confidently invoke this tool without risking misuse or misunderstanding.

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 schema description coverage is 100%, so all 19 parameters are documented in the schema itself. The description adds no parameter-specific information beyond the general update context. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description, as the schema already provides the necessary details.

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 ('Update') and resource ('existing activity in Pipedrive'), making the purpose immediately understandable. It distinguishes from sibling 'pipedrive_create_activity' by specifying 'existing' and from 'pipedrive_delete_activity' by being an update rather than deletion. However, it doesn't explicitly differentiate from other update tools like 'pipedrive_update_deal' 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 implied usage guidance with 'Use this to mark activities as done,' suggesting a common use case. However, it doesn't explicitly state when to use this tool versus alternatives (e.g., 'pipedrive_create_activity' for new activities or 'pipedrive_get_activity' for viewing), nor does it mention prerequisites like needing an existing activity ID. The guidance is helpful but incomplete.

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