Pipedrive MCP Server

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: the tool's dependency on visibility settings (access control), the condition under which it returns a 404 error (inaccessible thread), and that it returns a thread with messages (output format). This covers important aspects like error handling and output structure, though it doesn't mention rate limits or authentication requirements.

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 and well-structured in just two sentences. The first sentence states the core purpose, and the second provides crucial behavioral context about access control and error conditions. Every word earns its place with no redundancy or wasted 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 that there's no output schema and no annotations, the description does a good job of providing necessary context. It explains what the tool returns ('a mail thread with messages'), access dependencies, and error behavior. For a simple read operation with one parameter, this is reasonably complete, though it could potentially mention if the response includes metadata beyond messages.

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 input schema has 100% description coverage, with the 'id' parameter documented as 'Mail thread ID.' The description doesn't add any additional semantic information about this parameter beyond what the schema provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter info in the description.

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 a mail thread with messages.' It specifies the resource (mail thread) and what it returns (thread with messages), distinguishing it from sibling tools like pipedrive_get_mail_message which retrieves individual messages. However, it doesn't explicitly differentiate from pipedrive_list_mail_threads, which likely lists threads rather than fetching a specific one.

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 usage: 'Access depends on visibility settings - threads visible within deals/persons you can access should work.' This gives guidance on when the tool will succeed based on user permissions. It also mentions 'Returns 404 if the thread isn't accessible to you,' indicating failure conditions. However, it doesn't explicitly state when to use this tool versus alternatives like pipedrive_get_mail_message or pipedrive_list_mail_threads.

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