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

The annotations already convey that the tool is mutating, idempotent, and non-destructive. The description goes further by disclosing the exact side effects: pausing flips the cron runner flag without altering the published graph, and resuming re-anchors to now rather than replaying missed slots. It also adds the authentication scope requirement, which is not present in annotations.

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 three sentences, front-loads the primary action, and every sentence earns its place: the first states the operation, the second explains behavioral nuance, and the third covers prerequisites and authoring context. There is no filler or redundant restating of the tool name.

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 tool with no output schema, the description is complete. It explains both operational states, the effect on the deployed graph, the behavior on resume, the required scope, and how schedules are authored/armed. No critical information needed to call the tool correctly is missing.

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 schema documents the `paused` parameter but not `pipelineId`. The description partially compensates by clarifying that pipelineId refers to a published pipeline's schedule, adding semantic context that the bare schema does not provide. Since coverage is exactly 50%, the description contributes useful meaning beyond the structured field definitions.

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 ('pause or resume') and a well-defined resource ('a published pipeline's schedule'), which clearly differentiates it from siblings like run_pipeline or update_pipeline. It also explains how schedules are authored and armed, grounding the tool's role in the larger pipeline lifecycle.

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 description gives clear context on when to use the tool: it applies to published pipeline schedules and explicitly requires the pipelines:write scope. It does not name alternatives or explicitly say 'use this instead of X', but the singular focus on schedule pausing/resuming, plus references to get_node_type and publish_pipeline, gives an agent enough situational guidance.

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