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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds that the returned revision includes its blocks, which is genuine value. It does not mention error behavior for nonexistent revisions or the structure of the returned blocks; no output schema compensates.

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?

A single compact sentence with no filler, and the key information (single revision, any state, includes blocks) 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?

For a two-parameter read tool with full annotation coverage and no output schema, the description covers what it does and what it returns ('with its blocks'). Minor gap: no mention of how revisions relate to references or what happens if the revision number is invalid.

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 both parameters are documented in-schema, including that revision numbers come from list_pipeline_revisions and that 'entry' is a valid key. The description adds nothing beyond the schema, so the baseline 3 applies.

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 (Read) and resource (one pipeline revision) with an explicit scope qualifier ('active or not') and the payload ('with its blocks'). It distinguishes 'one' from the sibling list_pipeline_revisions by implication, though it doesn't name any sibling explicitly.

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?

'Active or not' implies you don't need to activate a revision first, which is useful context. But there is no explicit guidance on when to use this versus list_pipeline_revisions, get_pipeline, or get_pipeline_revision_references — the agent must infer from tool names.

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