Pipedrive MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'List all users' implies a read-only operation, it doesn't specify whether this requires authentication, any rate limits, pagination behavior, or what the return format looks like (e.g., list of user objects). For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 two concise sentences that are front-loaded with the core purpose and followed by a practical usage tip. Every word earns its place, with no redundancy or fluff, making it highly efficient and easy to parse.

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 tool's simplicity (0 parameters, no output schema), the description is adequate but incomplete. It explains the purpose and a use case but lacks details on behavioral aspects like authentication needs, response format, or error handling. With no annotations to fill these gaps, the description should do more to be fully complete for agent use.

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 tool has 0 parameters, and the schema description coverage is 100% (empty schema is fully described). The description doesn't need to explain any parameters, which is appropriate. A baseline of 4 is given since no parameters exist, and the description doesn't introduce any confusion about inputs.

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 ('all users in the Pipedrive account'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'pipedrive_get_user' by indicating it returns all users rather than a specific one. However, it doesn't explicitly differentiate from other list tools (e.g., 'pipedrive_list_organizations'), which prevents a perfect score.

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 clear context for when to use this tool: 'Useful for finding owner IDs when creating or filtering records.' This gives practical guidance on its application. However, it doesn't explicitly state when NOT to use it or name alternatives (e.g., using 'pipedrive_get_user' for a specific user), which would be needed for a score of 5.

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