pipedrive_bulk_add_deal_products

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

Annotations already establish a write operation (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds the batch-size ceiling ('up to 100'), which is useful. However, it does not disclose failure semantics for bulk operations (e.g., partial success, all-or-nothing validation) or whether the call appends to or replaces existing products, leaving openWorldHint=true under-explained.

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?

A single, front-loaded sentence with zero filler. The key qualifiers 'Bulk', 'up to 100', and 'in one request' all precede the noun and convey maximum meaning in minimal space.

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 bulk mutation with a complex nested payload (11 properties across line items) and no output schema, the description is thin. It leaves undefined what happens on partial failure, how existing deal products are affected, and whether items validate atomically. The rich schema covers parameters, but behavioral context for a bulk write is missing.

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% and the nested data array properties (tax, discount, billing_frequency, etc.) are fully documented in the schema. The description adds no parameter-level detail, so the dimension sits at the baseline where the schema carries the weight.

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 ('Bulk-add'), resource ('line-item products'), target ('a deal'), and a batch limit ('up to 100'). The 'bulk' qualifier distinguishes it from pipedrive_add_deal_product and pipedrive_update_deal_product, though it never names them explicitly.

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 implies the batch context ('up to 100 line-item products in one request') and contrasts implicitly with single-item siblings, but it does not explicitly state when to prefer this tool over pipedrive_add_deal_product or note any exclusions or prerequisites.

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