pipedrive_add_deal_product

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the agent knows this is a write operation that is not destructive. The description adds 'attach' but reveals no further behavioral traits, such as whether the deal total is recalculated, whether the product must exist, or what happens on failure. It does not contradict annotations, but adds minimal value beyond them.

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 a single, front-loaded sentence with no redundant or filler content. It clearly states the action and object in minimal words, making it very concise 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 tool has 14 parameters including optional billing fields and multiple sibling tools for deal products, a one-line description is insufficient. It does not explain when to use this versus bulk operations, mention prerequisites like existing deal/product IDs, or highlight notable optional behaviors (e.g., recurring billing). The agent would need to rely heavily on the schema and sibling names, risking incorrect selection.

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%, meaning all 14 parameters already have descriptive text in the schema. The tool-level description does not add any parameter-specific context beyond what the schema provides, so the baseline score of 3 is appropriate.

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 states a specific verb ('attach'), a specific resource (a single product as a line item to a deal), and it distinguishes itself from siblings like pipedrive_bulk_add_deal_products and pipedrive_update_deal_product by emphasizing 'single' and the add semantics. An agent can immediately understand the core function and differentiate it from related tools.

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 is provided about when to use this tool versus alternatives like bulk_add_deal_products or update_deal_product. The description does not mention any conditions, prerequisites, or contexts, leaving the agent to infer usage solely from the operation name and schema.

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