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

Annotations already declare that this is a write, destructive and open-world operation, but the description adds material context beyond that: the action carries cost ('paid research authority'), binds the exact saved revision hash, runs within the saved limits, requires pipelines:approve, and leaves delivery independently controlled. These are real operational constraints an agent cannot get from the annotations. What is missing is reversibility, such as how to revoke the standing authority, and what happens if the pipeline is already active.

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 dense but front-loaded: the core act and its precondition come first, followed by the binding and permission details. The only weak spot is the interruption with 'A second sample is optional', which is useful but awkwardly placed in the middle of the requirements sentence. Every sentence 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?

There is no output schema and no annotation depth on cost or permission, yet the description covers the paid and irreversible nature of the action, the exact revision binding, the required scope and the independent delivery control. What is still missing is what the call returns (activation status or id) and how the standing authority is revoked. Those gaps are real, but the critical facts for calling a destructive, paid tool correctly are present.

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 has to carry the parameter semantics alone. It does add meaning: revisionHash is tied to the reviewed saved revision, reviewedSampleRunIds is covered by 'A second sample is optional', and the requirements/limits that activation binds are spelled out. However, requestId's role (presumably idempotency) and the pipelineId and revisionId relationship are not explained, even though the revision binding is. This partial compensation is consistent with a 3 when all five parameters lack schema documentation.

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 uses a specific verb and resource: it grants standing paid research authority for a saved pipeline revision and enables recurring discovery. It implicitly separates activation from sampling work ('A second sample is optional'), which distinguishes it from prepare_pipeline and run_pipeline_sample. It stops short of naming the sibling tools outright, so the differentiation is inferred rather than stated.

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?

It gives a clear precondition: activate only after the user reviews the exact saved structured requirements, preferences, exclusions, contact routes, source configurations and limits, and only with the pipelines:approve permission. It also clarifies that a second sample run is optional rather than required. It never states when the agent should prefer update_pipeline or prepare_pipeline instead, and gives no when-not guidance.

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