create_a_pipeline

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

Annotations already indicate readOnlyHint=false and idempotentHint=false. The description reinforces these by stating 'WRITE', 'creates data', and 'Not idempotent — calling twice may create duplicates.' This adds slightly more context (the duplication warning) but does not disclose potential side effects, error conditions, or authorization needs beyond what is implied.

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 short but contains redundant statements: 'Create a pipeline' repeated three times. The first line is informative but could be integrated. It is not excessively long, but it could be more concise and better structured (e.g., front-loading the key action and non-idempotent warning).

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 nested input schema and no output schema, the description lacks essential context about what a pipeline is, how the dealGroup relates, return values, error handling, or any domain-specific knowledge. The agent may need to infer the purpose from the schema alone, which is insufficient for a complex creation tool.

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?

Input schema coverage is 100% with detailed descriptions for each property. The tool description does not add any additional meaning or examples for parameters, relying entirely on the schema. Per guidelines, baseline is 3 when schema coverage is high, and the description adds no extra value.

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 'Create a pipeline' and identifies it as a POST /dealGroups operation. It specifies the resource (pipeline/deal group) and action (create), making the purpose unambiguous. However, the repetition of 'Create a pipeline' adds noise, and it does not explicitly distinguish from other creation tools beyond the resource name.

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 mentions it's a write operation and not idempotent, but provides no guidance on when to use this tool versus alternatives (e.g., create_a_deal_new or others). There are no prerequisites, context, or exclusion criteria, leaving the agent without clear decision support.

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