pipelines_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. It states this is a creation tool ('Create new Heroku deployment pipelines') and mentions it 'manages pipeline creation with optional team and initial app configuration,' which implies mutation capabilities. However, it doesn't disclose permission requirements, rate limits, or what happens when creating duplicate pipelines, leaving behavioral gaps.

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 efficiently structured with two sentences: the first states the purpose, the second provides usage guidelines and additional context. Every sentence earns its place with no wasted words, and the bullet-point style use cases are front-loaded for quick scanning.

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?

For a creation tool with no annotations and no output schema, the description provides good contextual coverage. It clearly explains what the tool does and when to use it. However, it doesn't describe what the tool returns or potential error conditions, which would be helpful given the absence of output schema.

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 description coverage is 100%, so the schema already fully documents all four parameters. The description mentions 'optional team and initial app configuration,' which aligns with the schema but doesn't add meaningful semantic context beyond what's already in the structured fields. Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('Create new Heroku deployment pipelines') and resource ('pipelines'), distinguishing it from sibling tools like create_app or deploy_to_heroku. It provides a precise verb+resource combination that leaves no ambiguity about what this tool does.

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 explicitly lists four specific use cases when to use this tool: 1) Set up new deployment workflows, 2) Create staged application environments, 3) Organize apps by development stages, 4) Configure team-based pipeline structures. This provides clear guidance on appropriate contexts for tool selection.

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