Create Pipeline

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds valuable context about visibility semantics (Public vs TeamSharing) and the team_ids requirement. However, it omits other behavioral aspects like return value, side effects, or default stages, leaving gaps for a creation tool.

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 concise and front-loaded, with the main action stated first. Every sentence adds value, covering purpose and permission details without redundancy or fluff.

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 4 parameters with full schema coverage and no output schema, the description adequately covers the core purpose and permission behavior. It could mention the response or additional effects, but the provided information is sufficient for a create operation with clear sibling context.

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?

The schema already provides 100% coverage for parameter descriptions, establishing a baseline of 3. The description adds conceptual meaning beyond the schema by explaining what Public and TeamSharing mean (visible to all users vs specified teams), which enriches understanding of the parameters.

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 tool creates a new pipeline in Less Annoying CRM, with a specific verb ('Create') and resource ('pipeline'). It also explains what pipelines are, and the operation is distinct from sibling tools like edit_pipeline and delete_pipeline.

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 clear context on when to use Public vs TeamSharing permissions and specifies that TeamSharing requires team_ids, which guides parameter usage. However, it does not explicitly contrast with alternative tools, though the create operation is self-evident.

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