Create pipelines

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

The description discloses that the tool can create multiple pipelines in one call ('one or more') and can optionally include stages. This goes beyond the bare action, but it does not disclose permissions, idempotency, or side effects. The openWorldHint annotation does not cover safety aspects, and no contradictions exist.

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 a single, concise sentence that front-loads the verb and resource. Every word adds context, with no filler or redundancy.

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?

The description is too sparse for a create tool with a permissive schema and no output schema. It does not specify required fields for a pipeline (e.g., name) or how to structure nested stages. The openWorldHint annotation hints at flexibility, but the description fails to guide an agent on how to construct a valid request.

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?

With 0% schema description coverage, the description must compensate for the lack of parameter details. It does mention that the 'pipelines' parameter is an array of pipeline objects and may include stages, providing some semantic hint. However, it still leaves the internal structure of each pipeline unspecified, which is insufficient given the schema's generic additionalProperties.

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 the resource ('pipelines'), with scope ('one or more') and an optional feature ('with stages'). This distinguishes it from sibling tools like kommo_pipelines_list, kommo_pipelines_update, and kommo_pipelines_delete.

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 usage for creating pipelines but provides no explicit guidance on when to use this tool versus alternatives such as kommo_stages_create. It does not mention any exclusions or preconditions, leaving the agent to infer the appropriate context.

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