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 adds valuable context about access dependencies and visibility settings, which goes beyond basic functionality. However, it doesn't mention potential error conditions, rate limits, authentication requirements, or what happens when include_body is set to false versus true.

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 perfectly concise with two sentences that each earn their place. The first sentence states the core purpose, and the second provides crucial access context. There's zero wasted language or redundancy.

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 read operation with no annotations and no output schema, the description provides adequate but incomplete context. It covers the purpose and access constraints well, but doesn't describe the return format, error conditions, or what 'full email message' includes beyond the body. Given the complexity and lack of structured metadata, it should do more to be fully complete.

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 both parameters thoroughly. The description doesn't add any additional parameter semantics beyond what's in the schema (id as 'Mail message ID' and include_body with its default). This meets the baseline expectation when schema coverage is complete.

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 tool's purpose: 'Get full email message with body.' It specifies the resource (email message) and the key capability (including body). However, it doesn't explicitly differentiate from sibling tools like pipedrive_get_mail_thread or pipedrive_get_deal_emails, 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 about when the tool works: 'Access depends on visibility settings - messages linked to deals/persons you can access should work, even if sent by other users.' This gives practical guidance on access permissions. However, it doesn't explicitly state when NOT to use this tool or name specific alternatives among the siblings.

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