pipedrive_leads_create

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

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It discloses only the person/organization constraint; it omits permission requirements, whether a duplicate/conflicting lead is rejected, and what side effects creation triggers. That single constraint is useful but far from adequate for an unannotated create operation.

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?

Two short sentences, zero filler, with the core action front-loaded and the key constraint immediately after. Every clause earns its place.

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 an 8-parameter mutation tool with no annotations and no output schema, the description is thin: it covers the operation and one precondition but says nothing about side effects, permissions, or failure modes. The rich 100% schema coverage compensates for parameter-level gaps, landing it at minimum-viable rather than incomplete.

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 all 8 parameters, establishing a baseline of 3. The description adds the cross-parameter constraint that at least one of person_id or organization_id must be supplied, which is genuine value the schema does not express, keeping it at the baseline rather than below it.

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 opens with a specific verb+resource ("Create a new lead") that an agent can distinguish from siblings such as pipedrive_leads_update, pipedrive_leads_delete, and pipedrive_leads_get by name. It does not explicitly state how it differs from leads_search or other create tools, but the resource and operation are unambiguous.

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 second sentence gives a meaningful precondition ("Requires at least person_id or organization_id"), which is genuine usage guidance. However, there is no explicit when-to-use vs alternatives routing (e.g., leads vs deals) and no when-not-to-use guidance, so it remains implied rather than directive.

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