pipedrive_deals_create

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

The description mentions support for custom fields by name or key, which is a useful behavioral trait. However, with no annotations, it lacks disclosure on permissions, rate limits, or side effects. The brief description barely covers behavioral transparency.

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 concise with two sentences, no waste. However, it could be structured to front-load critical information like required fields.

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 creation tool with 12 parameters and no output schema, the description is too minimal. It does not explain the deal's lifecycle, return values, or how custom fields interact with the rest of the parameters.

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 value for custom_fields and custom_fields_by_name parameters, but schema coverage is only 8%. Most parameters lack description, and the description does not explain their purpose beyond what the schema types imply.

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 creates a new deal and supports custom fields. It distinguishes from sibling tools like pipedrive_deals_update or pipedrive_deals_list by focusing on creation, but could be more specific about the deal structure.

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?

No guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as requiring a person or organization to exist, nor does it indicate when to use pipedrive_deals_update for modifications.

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