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

With no annotations, the description carries the full burden, and it does well: it discloses ordering (newest first), the non-obvious merge behavior of consecutive manual UI edits into one revision, and the pagination mechanism. It stops short of stating read-only/scope guarantees or the effective limit ceiling, but the genuinely surprising behavior is surfaced.

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?

Three short units, front-loaded with purpose followed by the return shape, merge semantics, and pagination hint. The inline field enumeration is long but earns its place as the only return-shape documentation available.

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 read tool with no output schema and no annotations, the description supplies the return structure, ordering, revision-merging rule, and cursor pagination — enough to call it correctly. The gap is the `limit` parameter's bounds and whether history is complete or truncated.

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 must compensate. It explains `before_seq` as the pagination cursor and ties `seq` to the returned fields, but leaves `limit` (default 30, maximum?) and `pipeline_id` format entirely undocumented in both schema and description.

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?

Opens with a specific verb-resource pair ('Change history of a pipeline, newest first'), so an agent immediately knows this is the revision-list read. It never names or distinguishes itself from the sibling pipeline_history_get, which presumably fetches a single revision, so the boundary is left implicit.

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 explicit when-to-use or when-not guidance, and no mention of pipeline_history_get or pipeline_history_restore as alternatives. The only usage-adjacent text is 'Page with `before_seq`', which covers iteration but not tool selection.

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