pipeline_set_config_tool

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

With no annotations, the description carries the full burden, and it discloses almost nothing: whether this mutates persistent state or only a session working set, what 'reset' destroys, whether omitted params are preserved or cleared, and whether concurrent GUI/agent writes conflict. The phrase 'shared GUI/agent' hints that the change is visible to both surfaces, which is the only real behavioral signal.

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?

It is a single front-loaded sentence with no padding, which is good. But the brevity comes at the cost of substance rather than being efficient density.

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 state-mutating configuration tool with five undocumented optional parameters and no annotations, the description leaves critical behavior unstated. The presence of an output schema excuses it from describing returns, but not from the missing mutation semantics.

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 0% across five parameters, and the description only vaguely gestures at config via '(visible params)'. It never explains reset (full replace?), unattended (auto-confirm?), project_path, or enabled_steps, so an agent cannot construct a non-trivial call without guessing.

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 states a verb ('Update') and a resource ('shared GUI/agent pipeline working set'), so the general intent is inferable. However, 'working set (visible params)' is jargon that doesn't pin down what is actually being changed, and it never distinguishes itself from the obvious sibling pipeline_get_config_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?

There is no guidance on when to use this versus pipeline_get_config_tool, pipeline_run, or pipeline_analyze_tool. It also doesn't say whether to read current config first via the getter or what happens on the first call vs. subsequent ones.

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