ghl_pipeline_create

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it fails to mention any side effects, permissions, or return behavior. The agent has no idea what happens when a pipeline is created, what the response is, or whether it requires special authorization.

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?

While the one-line description is efficient, it is too sparse to convey essential information. The brevity comes at the cost of under-specification, making this more of a stub than a well-structured tool description.

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 tool has no output schema, no annotations, and a minimal description, the agent lacks context about the creation process, return values, or side effects. The schema covers parameters, but everything else is missing, making the description incomplete for practical use.

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 input schema covers 100% of parameters with descriptions, including the default behavior for locationId, so the baseline is 3. The tool description itself adds no parameter semantics beyond what the schema already provides, but the schema is sufficient.

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 'Create a pipeline' uses a specific verb and resource, clearly indicating the tool's function. However, it doesn't provide additional details to distinguish it from other create tools for different resources or from the sibling pipeline-stage creation tool.

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 gives no guidance on when to use this tool versus alternatives such as ghl_pipeline_update or ghl_pipeline_delete. It also doesn't mention any prerequisites or context, leaving the agent without decision-making information.

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