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 it creates a deal but doesn't cover critical aspects like authentication requirements, rate limits, whether the operation is idempotent, what happens on failure, or the expected response format. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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—with zero wasted words. It's front-loaded with the core action and immediately states the key constraint about required fields, making it 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 complexity (15 parameters, mutation operation, no annotations, and no output schema), the description is inadequate. It doesn't explain what a successful creation returns, error handling, or how to interpret parameters like 'visible_to' or 'custom_fields' beyond the schema. For a tool of this scope, more contextual information 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?

The description adds minimal value beyond the input schema, which has 100% coverage. It clarifies that 'title is required' and 'all other fields are optional,' but this is already implied by the schema's required array and property descriptions. No additional context, examples, or constraints are provided for the 15 parameters.

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 ('Create') and resource ('new deal in Pipedrive'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like pipedrive_update_deal or pipedrive_list_deals, which would require mentioning it's for initial creation only.

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 minimal guidance by noting 'Only title is required; all other fields are optional,' but offers no context on when to use this tool versus alternatives like pipedrive_update_deal for modifications or pipedrive_list_deals for viewing. There's no mention of prerequisites, error conditions, or typical use cases.

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