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

Goes well beyond the annotations: it explains that every trigger on the target status is sent with fire=false, that CATS enforces trigger semantics while externally configured webhooks may still fire, that the change is written to status history, and gives the underlying POST /pipelines/{id}/status endpoint. That is meaningful side-effect disclosure for a destructive, non-idempotent operation.

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?

Front-loaded with the WRITE marker and the confirm requirement, and most sentences carry distinct information (ID sources, trigger suppression, history, endpoint). The phrase 'Requires confirm:true' appears twice, which is wasted repetition in an otherwise tight 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 3-parameter mutation tool with no output schema, the description covers the safety gate, side effects, and ID provenance, which is nearly everything an agent needs. The only omission is any statement about the response body or what the agent should verify afterward, which is a minor gap given there is no output schema.

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 coverage is 100%, so the baseline is 3; the description adds value by naming the source tools for pipeline_id and status_id and reinforcing that the status must belong to the pipeline's workflow. It still doesn't clarify the exact semantics of the 'confirm' flag beyond restating the requirement.

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?

States a specific verb and resource ('change the status of a pipeline') and immediately glosses it as moving a candidate between workflow stages with concrete examples (Interviewing, Offered, Rejected). This is clearly distinguishable from read-oriented siblings like cats_get_pipeline or cats_list_workflow_statuses.

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?

Explicitly routes the agent to cats_list_candidate_pipelines for the pipeline id and cats_list_workflow_statuses for the status id, which is exactly the prerequisite chain an agent needs. It lacks an explicit 'do not use when…' clause (e.g., for creating a new pipeline or adding an activity), so it falls short of a 5.

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