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 a creation operation, implying mutation, but lacks details on permissions needed, whether it's idempotent, rate limits, error handling, or what the response looks like (e.g., returns the created person object). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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—just one sentence that directly states the purpose and key constraint. It's front-loaded with the core action and wastes no words, making it easy for an agent to parse quickly without unnecessary elaboration.

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 (10 parameters, nested objects, no output schema, and no annotations), the description is inadequate. It doesn't explain return values, error conditions, authentication requirements, or how this tool fits into the broader Pipedrive context compared to siblings. For a mutation tool with rich input schema but no other structured data, more descriptive context is needed.

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%, so the schema already documents all 10 parameters thoroughly. The description adds minimal value by noting that 'Only name is required,' which is already clear from the schema's required array. It doesn't provide additional context like typical values or usage examples beyond what the schema offers, meeting 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 ('Create a new person') and resource ('in Pipedrive'), with the specific note that 'Only name is required' adding useful constraint information. However, it doesn't differentiate this from sibling tools like 'pipedrive_create_organization' or 'pipedrive_create_deal' beyond mentioning 'person (contact)', which is somewhat implicit but not explicit about when to choose this over other creation tools.

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 like 'pipedrive_create_organization' or 'pipedrive_update_person', nor does it mention prerequisites (e.g., authentication needs) or typical use cases. The only usage hint is the requirement that 'Only name is required,' which is a parameter constraint rather than contextual guidance.

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