pipedrive_products_create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure for a mutation tool. It reveals nothing about side effects, required auth scopes, whether it errors on duplicate names, what a successful response contains, or how nested prices are applied. The sentence is effectively a restatement of the tool name.

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 single sentence is front-loaded and free of waste, but for a 10-parameter mutation tool with nested objects it is under-specified rather than genuinely concise. Appropriate sizing would warrant at least a note on the required field and nested price structure.

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?

With 10 parameters including a nested prices array, no output schema, and no annotations, the description supplies none of the behavioral context an agent needs to call this safely. The rich schema partially compensates for parameter documentation, but creation semantics, validation behavior, and return shape are entirely absent.

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 90%, with clear per-field descriptions and an explicit enum explanation for visible_to, so the schema does the heavy lifting. The description adds no parameter meaning of its own, which is the baseline 3 when schema coverage is high.

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 and resource ('Create a new product'), which is unambiguous about the operation. However, it does nothing to distinguish this tool from the many siblings that also create product-related entities, such as pipedrive_product_variations_create or pipedrive_deal_products_add, nor does it clarify scope (e.g. catalog-level vs deal-level).

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?

There is no guidance on when to use this tool versus alternatives like pipedrive_product_variations_create or pipedrive_products_update, and no mention of prerequisites such as required permissions or duplicate handling. The agent must infer usage entirely from the name.

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