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

With no annotations and no output schema, the description carries the burden and does disclose useful return behavior: it explains that snapshot is the full pipeline state after the change and diff is versus the previous revision. However, it does not state that the operation is read-only, whether permissions are required, or what happens on invalid IDs.

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?

It is a single compact sentence that front-loads the key fact ('One revision') and avoids waste. The fragmentary notation makes it slightly less clear than it could be, but it is not bloated.

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 tool with two required, undescribed parameters and no annotations or output schema, the definition is under-specified. It gives useful return-field context but leaves the input semantics and basic operational behavior to inference.

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?

The description does not mention pipeline_id or revision_id at all. With 0% schema description coverage on two required parameters, it fails to compensate for the missing 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 says 'One revision' and lists the returned fields, implying retrieval of a single pipeline revision, but it never states the action or resource explicitly. The sibling pipeline_history_list exists, and the contrast between 'One revision' and a list is implied rather than spelled out.

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?

There is no guidance on when to use this tool versus alternatives, including the obvious sibling pipeline_history_list. The description also omits any prerequisites such as needing a valid pipeline_id or revision_id.

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