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. While 'Create' implies a write/mutation operation, the description doesn't address important behavioral aspects: whether this requires specific permissions, what happens on success/failure, whether activities are immediately visible in the system, or any rate limits. It mentions required parameters but doesn't explain the broader behavioral context of activity creation in Pipedrive.

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 at just two sentences with zero wasted words. It's front-loaded with the core purpose and follows with the most critical implementation detail (required parameters). Every sentence earns its place, making it efficient for an agent to parse while conveying essential information.

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 19 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what constitutes a successful creation, what data is returned, error conditions, or how this tool fits into broader Pipedrive workflows. The comprehensive schema helps, but the description should provide more context about the tool's behavior and integration points.

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 adds minimal parameter information beyond the schema. It mentions that 'subject and type are required,' which the schema already indicates with its required array and parameter descriptions. With 100% schema description coverage, the baseline is 3, and the description doesn't significantly enhance understanding of parameter meanings, relationships, or usage patterns beyond what's already documented in the comprehensive 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 verb ('Create') and resource ('new activity in Pipedrive'), making the purpose unambiguous. It distinguishes this tool from sibling tools like pipedrive_update_activity or pipedrive_delete_activity by specifying it's for creation, but doesn't explicitly differentiate from other creation tools like pipedrive_create_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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when to choose this over pipedrive_update_activity for modifications, or how it relates to pipedrive_list_activities for viewing existing activities. The only usage hint is the statement about required parameters, which is better categorized under parameter semantics.

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