trmnl_pipeline_enable

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

Annotations already declare the operation is not read-only, not destructive, not idempotent, and not open-world. The description adds that it only toggles publishing state and does not create a schedule, but it does not describe permissions, side effects, or response behavior.

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 short sentences, front-loaded with the core purpose and followed by a useful exclusion. Every sentence carries information relevant to invoking the tool correctly.

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 simple two-parameter toggle with annotations covering safety traits and no output schema, the description is largely complete. It could be stronger by explicitly tying `enabled=true` to enabling and `enabled=false` to pausing, but the core behavior and non-schedule scope are clear.

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?

With 0% schema description coverage, the description partially compensates by implying that `id` identifies a saved pipeline and that `enabled` toggles publishing on or off. However, it does not explicitly map true/false to enable/pause or clarify the id format beyond what the schema's pattern already provides.

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 specific verb and resource: "Enable or pause publishing" for "one saved pipeline." It also explicitly excludes creating a schedule, which helps distinguish it from schedule-related tools, though it does not name a specific sibling alternative.

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?

The intended use is clear: toggle publishing for a saved pipeline. The sentence "Does not create a schedule" provides a useful exclusion against schedule_plan, but the description does not name alternatives such as pipeline_run or pipeline_save.

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