pipeline_apply_fixes

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

Annotations mark this as a write (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds genuinely new context: the original final is preserved (consistent with destructiveHint=false) and a fresh diff-only confirmation is required before approval. That workflow constraint is not derivable from any structured field. It still doesn't say what happens when an 'old' string is not found or when the run isn't in STOP state.

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 sentences, no filler, with the core action front-loaded and the safety constraint second. Dense with domain terms but every clause carries information.

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 non-idempotent, two-parameter mutation tool with no output schema, this covers the essentials: authorization source, target artifact, preservation guarantee, and confirmation gate. It omits error/rejection semantics and the batch-size limit, leaving meaningful gaps for an agent orchestrating a pipeline run.

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%, so the description must carry the load. It does convey that replacements are exact old-string matches, which explains the old/new pair semantics and implies literal matching rather than regex. But it says nothing about the 1–10 item cap on 'fixes', the run_id format, or failure behavior for unmatched strings.

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 verb+resource is specific: 'Apply explicit Judge-authorized exact replacements to a STOP final.' It identifies the operation on a distinct artifact state ('STOP final') within the pipeline family. It stops short of naming a sibling to distinguish it from, and the domain jargon ('Judge-authorized', 'STOP final') assumes insider knowledge.

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 prerequisite is implied through 'Judge-authorized' and 'STOP final' — an agent can infer this runs only after a Judge verdict on a stopped run. However, there is no explicit when-to-use statement, no when-not-to-use, and no named alternative among siblings like pipeline_submit or pipeline_resume.

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