pipelines_edit

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

Annotations indicate readOnlyHint=false, so the description's 'Edit' is consistent with a mutation operation. The description does not add any extra behavioral details beyond the verb, such as whether it's a partial update, what happens on error, or if it triggers a pipeline restart. With annotations handling basic behavior, this is adequate but not enhanced.

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, but it is too minimal to provide useful structure. Could be improved by listing key modifiable fields or usage notes.

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 19 parameters, 1 required, and low schema coverage, the description is incomplete. It does not explain common editing scenarios, constraint, or the fact that all parameters except pipeline_id are optional, implying partial updates. An output schema exists but is not referenced.

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 only 11% (only pipeline_id has a description). The tool description does not add any parameter details, leaving 17 parameters underdocumented. For low coverage, the description should compensate, but it does not.

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 verb 'Edit' and the resource 'pipeline', and provides the API endpoint, which distinguishes it from sibling tools like pipelines_create, pipelines_get, etc. However, it could be more explicit about modifying an existing 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?

No guidance on when to use this tool vs alternatives, such as pipelines_create for new pipelines, or when not to use it. No prerequisites mentioned (e.g., pipeline must exist).

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