pipedrive_create_pipeline

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

Annotations already indicate it's not read-only, not destructive, not idempotent, and open world. The description adds that name is required and that is_deal_probability_enabled controls weighted probability. However, it does not disclose potential side effects (e.g., pipeline creation implications) or authentication requirements, but this is acceptable given annotations cover the safety profile.

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?

Two well-structured sentences with no redundancy. The first sentence states the primary action, the second adds parameter details. Efficient and front-loaded.

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 simplicity (2 params, no nested objects) and no output schema, the description is mostly adequate. However, it lacks any information about the return value or expected response, which would help an agent understand what to do after creation. This is a minor gap given the tool's straightforward nature.

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 coverage is 100%, so the schema already describes both parameters. The description adds value by clarifying that name is the only required field and explaining the purpose of is_deal_probability_enabled ('turn on weighted deal probability'), which goes beyond the schema's simple type/description.

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 action ('Create') and resource ('new sales pipeline'), and specifies that only name is required. It distinguishes this tool from sibling tools like pipedrive_create_deal or pipedrive_create_phase by the unique resource (pipeline), but does not explicitly differentiate from similar pipeline-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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context of use, or when not to use it. The only instruction is that name is required and the optional boolean, but no broader usage context.

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