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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds value by explaining the null-clear behavior, the validation by org, and the org+mode resolution. It does not explicitly state that assigning a new pipeline overwrites an existing one, but the clear option implies this. Given annotation coverage, the additional context is solid.

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 fluff. The main action and clear behavior are front-loaded, with the validation details in the second sentence. Every word adds meaning, making it an efficient and well-structured description.

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 mutation tool with 4 parameters, no output schema, and 0% schema param coverage, the description is incomplete. It omits the meaning of job_id, request_id, and idempotency_key, and does not mention what happens on success (e.g., return value or side effects). The validation note is helpful but not enough to cover the gaps.

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 burden falls on the description to explain all 4 parameters. It only explains pipeline_id (including null semantics) and vaguely mentions job resolution, but job_id, request_id, and idempotency_key are left undocumented. This is a significant gap for a tool with several parameters.

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?

Clearly states the specific action: assign a pipeline to a job via the jobs.pipeline_template_id field, and explicitly covers the clear-with-null case. This differentiates it from generic job update or pipeline management tools; an agent knows exactly what this tool does and can distinguish it from siblings like yardstick_jobs_update.

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 a clear use context: assigning or clearing a pipeline on a job. It does not mention when to use an alternative (e.g., jobs_update), but the description is self-sufficient for typical usage. No exclusions or when-not cases are stated, so it earns a 4, not a 5.

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