pipeline.config

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the meaningful trait that the tool dispatches between read and merge-update based on presence of `config`, which is more than the name conveys. However, it says nothing about permissions, whether updates are reversible, how keys are validated, or whether fields can be cleared.

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?

Two tight clauses, front-loaded with the read/update purpose and finished with the mode-selection rule. The parenthetical field list is dense but every token carries information, and nothing is repeated.

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 nested-object mutation tool with no annotations and no output schema, the description is only partially sufficient: it explains the update trigger and lists config fields but omits what a read returns, sub-field types/defaults, and mutation side effects. Adequate to invoke, thin on guarantees.

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 coverage is 50%: `config` is documented (partial merge, omit to read) while `skill_id` is bare. The description compensates somewhat by enumerating the config sub-fields (max_latency_ms, enforce_latency/enforce_tests flags, default targets), adding meaning beyond the schema, but it gives no types, defaults, or merge-edge behavior.

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?

States a specific verb pair (read/update) and resource (a skill's pipeline_config), and enumerates the fields under management (max_latency_ms, enforce_latency/enforce_tests flags, default targets). It implicitly separates itself from pipeline.run/pipeline.status by scope, though it never names those siblings explicitly.

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?

Gives explicit mode-selection guidance: 'Pass `config` to update; omit to read.' That tells the agent exactly which invocation shape triggers which behavior. It stops short of naming alternatives or stating when-not-to-use it (e.g., vs pipeline.run for execution).

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