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

With no annotations provided, the description carries the full burden, and it does disclose genuinely non-obvious behavior: newest-first ordering, the merging of consecutive manual UI edits 'within a few minutes' into one revision, and the pagination field. It does not state that the operation is read-only nor mention any permission requirements, so the safety profile remains unstated.

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 compact sentences: return shape first, then the merging caveat, then pagination. The inline enum-style notation for action and source is dense but readable and front-loaded, with no filler.

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 or annotation coverage, so the description rightly spends its space describing the returned record fields and ordering, which is the main risk for this tool. The remaining gap is `limit` semantics and the lack of any alternate-tool routing, which keeps it from a 5.

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 supply parameter meaning. It explains `before_seq` through the paging hint, but `limit` (default 30, no bounds given) and its interaction with paging are never mentioned, and nothing clarifies what workflow_id must reference.

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 names the resource precisely ('Change history of a workflow') and specifies ordering ('newest first') plus the exact record shape returned. It never explicitly contrasts itself with the sibling workflow_history_get or workflow_history_restore, so an agent must infer the list-vs-single-vs-mutate split from names alone.

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 only usage instruction is 'Page with `before_seq`', which is pagination mechanics rather than when-to-use guidance. There is no statement of when to prefer this over workflow_history_get, nor any prerequisite such as needing the workflow_id first.

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