manage_pipeline

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

With no annotations provided, the description carries full burden for behavioral disclosure. It lists actions and parameters but omits important details such as permission requirements, side effects of each action, error handling, or irreversibility (e.g., delete is irreversible but not highlighted). The return is described vaguely as 'human-readable responses', which lacks specificity.

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 well-structured with a high-level overview, a bullet list of actions, and a parameter list. It avoids redundancy but is slightly lengthy. The information is front-loaded with the purpose, and each sentence contributes value. Minor conciseness improvements could be made.

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's complexity (12 parameters, multiple actions) and the presence of an output schema, the description covers most essential aspects: actions, parameters, and return type. However, it lacks explicit conditional requirements (e.g., which parameters are required for which action) and does not document error states or validation rules, leaving some gaps for an agent.

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 has 0% description coverage, so the description must fully explain each parameter. It does so effectively: each parameter in the Args section includes a brief description and, where applicable, example values (e.g., source: 'saved:weekly_search' or 'file:path/to/pipeline.yaml'). This adds significant meaning beyond the bare schema.

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 'Manage saved pipelines through a single facade' and then enumerates the specific actions (save, list, load, delete, history, schedule). This provides a precise verb+resource definition and distinguishes it from sibling tools that handle individual actions.

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?

While the description implicitly presents itself as a unified interface, it does not explicitly guide when to use this facade versus the individual sibling tools (e.g., save_pipeline, delete_pipeline). There is no 'when-not' or alternative selection advice, 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.