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

Annotations already declare this is a destructive, idempotent, non-read-only mutation, so the bar is lower. The description adds useful behavior: pipeline validation by org and job resolution by org+mode, plus the clear-with-null action. It still does not explain what assignment overwrites or how stage_mapping and idempotency behave.

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 a single front-loaded sentence that covers the main action and the clear case without filler. It is dense but appropriately sized for a tool definition, though the parenthetical and validation clauses make it slightly packed.

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 five-parameter mutation with a nested stage_mapping object and no output schema, the description covers only the core assignment/clear behavior. It leaves stage_mapping, idempotency_key, and request_id unexplained, which is a significant gap for correct invocation.

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 parameter meaning, and it partially does for job_id and pipeline_id. It says nothing about request_id, idempotency_key, or the nested stage_mapping object, leaving three of five parameters without any semantic guidance.

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: assign a pipeline to a job, and explicitly covers the clear case with pipeline_id: null. It is clear in isolation, but it does not differentiate from the sibling yardstick_pipelines_assign_to_job_preview, so an agent gets no direct routing hint between previewing and applying.

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 implies usage by explaining both assignment and clearing via null, which is more than nothing. However, it gives no when-not conditions and does not mention the preview alternative or any prerequisites for choosing this tool over yardstick_pipelines_assign_to_job_preview.

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