pipedrive_leads_create

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

With no annotations, the description carries full burden. It only states the creation action and a parameter constraint, but lacks info on side effects, permissions, idempotency, or return 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?

One sentence, front-loaded with action. Concise but could benefit from listing key optional parameters for quick reference.

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 8 parameters, nested objects, no output schema, and low schema coverage, the description is too sparse. It does not cover success behavior, error conditions, or relation to other entities.

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 coverage is only 13%, meaning most parameters are undocumented. The description adds value for the person_id/organization_id constraint but does not explain other parameters like owner_id, label_ids, value object, expected_close_date, or visible_to. Incomplete for a tool with 8 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?

Description clearly states 'Create a new lead', which is a specific verb+resource. This clearly distinguishes from sibling tools like pipedrive_deals_create or pipedrive_persons_create.

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?

Provides a constraint: 'Requires at least person_id or organization_id.' This gives some guidance on prerequisites, but no comparison to alternatives or when-not-to-use.

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