pipelines_start_update

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

Annotations indicate readOnlyHint=false (write operation), but the description adds no behavioral details beyond 'start'. It doesn't disclose side effects, required permissions, or what happens to the pipeline (e.g., triggers a run).

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 very concise: one sentence plus the endpoint URL. It is front-loaded with the action. However, it is almost too sparse, warranting a slight deduction from perfect.

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?

Despite having an output schema, the description is incomplete for a tool with 7 parameters. It lacks context on the update process, parameter effects, and potential outcomes, making it insufficient for proper tool invocation.

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 43% (3 of 7 parameters described). The description does not provide any additional context for parameters like full_refresh, refresh_selection, or rewind_spec beyond the schema, missing an opportunity to clarify their purpose.

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 'Start a pipeline update', which is a specific verb and resource. It distinguishes from sibling tools like pipelines_get_update, pipelines_list_updates, and pipelines_stop by focusing on initiating an update.

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 versus alternatives. Missing prerequisites such as pipeline existence or state (e.g., running). No mention of when not to use or related tools.

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