pipedrive_product_variations_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, and it discloses nothing: no permission/auth requirements, no reversibility, no side effects, and no note on the default pricing behavior. For a mutation tool this is a serious gap.

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 short, front-loaded sentence with zero wasted words. It is efficient, though the brevity here reflects under-specification rather than high information density.

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?

A create tool with no annotations and no output schema needs to convey required inputs and side effects. The description omits that product_id and name are required and says nothing about the prices default, leaving the agent dependent entirely on the schema.

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%, with the schema already documenting product_id, name, and the prices default in detail, so the schema does the heavy lifting. The description adds no syntax, format, or constraint information beyond it — the baseline 3 applies.

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?

"Add a variation to a product" names a specific verb (add/create) and resource (product variation) with the parent entity, so the agent knows the operation. However, it is largely a restatement of the tool name and does not distinguish it from the create/update/delete/list variation siblings.

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 versus pipedrive_product_variations_update or pipedrive_product_variations_list, nor any stated prerequisite (e.g. that the parent product must already exist). The create verb implies usage, but nothing is made explicit.

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