Pipedrive MCP Server

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

No annotations are provided, so the description carries full burden. It mentions 'optional filtering' but doesn't disclose key behavioral traits: pagination behavior (implied by cursor parameter but not explained), rate limits, authentication requirements, error handling, or what the response format looks like. For a list operation with 12 parameters, this is inadequate disclosure.

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 a single, efficient sentence that front-loads the core purpose ('List organizations from Pipedrive') followed by the key filtering options. There's zero wasted language, and every word earns its place in 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?

Given the complexity (12 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the response format, pagination strategy, error conditions, or authentication needs. While the schema covers parameters well, the description fails to provide the behavioral context needed for effective tool invocation in a real API integration scenario.

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 fully documents all 12 parameters. The description adds minimal value by mentioning filtering by 'owner or first letter of name' (covering owner_id and first_char), but ignores the other 10 parameters. This meets the baseline 3 for high schema coverage, but doesn't enhance understanding beyond what the schema provides.

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 'List' and resource 'organizations from Pipedrive' with optional filtering scope. It distinguishes from sibling tools like pipedrive_get_organization (singular fetch) and pipedrive_search_organizations (search vs list), though not explicitly named. However, it doesn't fully differentiate from pipedrive_list_organizations' own siblings that also list resources, making it a 4 rather than a 5.

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_search_organizations or pipedrive_get_organization. It mentions optional filtering but doesn't specify scenarios or exclusions. With many sibling tools available, this lack of comparative context leaves the agent without clear selection criteria.

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