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

Annotations already declare readOnly=true and destructive=false, so the safety profile is covered. The description adds real context beyond them: ordering of blocks, inclusion of the default escalation path, and that block shape is round-trippable into update_pipeline. It says nothing about behavior for an unknown pipeline_key or about revision metadata, keeping it below a 5.

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, both load-bearing: the first defines the return content, the second explains the downstream use. Nothing is redundant and the main scope statement is front-loaded.

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?

With no output schema, the description must carry the return shape, and it does cover blocks-in-order and the default escalation path. It omits error/not-found behavior and whether revision identifiers are included, which would make it fully complete for an agent planning a follow-up update.

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% and the single parameter is well documented in the schema, including the special 'entry' key, so the baseline of 3 applies. The description adds no parameter-level detail beyond what the schema already says.

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 ('Read a pipeline's active revision') plus scope (blocks in order, default escalation path). The word 'active' implicitly separates it from get_pipeline_revision and list_pipeline_revisions, but no sibling is named explicitly, so it stops short of a 5.

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 second sentence gives a concrete workflow context: the returned blocks are in the shape update_pipeline accepts, so this read feeds an edit-and-resubmit cycle. It does not state when to prefer get_pipeline_revision or list_pipelines instead, so there is no exclusion guidance.

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