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

Annotations are absent, so the description carries the full burden. It does disclose the return payload in useful detail (snapshot = full state after the change, diff = vs previous revision), but never states that this is a read-only operation, that it requires a valid workflow_id, or what happens when a revision is missing. Behavior on the success path is well covered; failure and safety behavior is not.

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 dense sentence that front-loads the resource ('One revision') before the payload shape. The brace notation is terse but each clause carries real information about the returned fields; nothing is padding.

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, and the description does a fair job of describing the return value, which is the main gap it needed to fill. But with two undocumented required parameters and no notes on obtaining a revision_id, it is only partially complete for a lookup tool.

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% for two required parameters. The description implies 'revision' semantics but never explains whether revision_id is an index, a hash, or a version label, nor how workflow_id relates to it. The agent would still need to guess at argument format.

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?

'One revision:' plus an explicit enumeration of the returned payload makes it clear this fetches a single historical revision rather than a list, implicitly distinguishing it from workflow_history_list. It stops short of a real verb phrase ('get one workflow revision'), so the agent must infer retrieval from the field list, but the singular 'One' carries the scope distinction.

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?

No when-to-use guidance at all: no mention of when to pick this over workflow_history_list, workflow_get, or workflow_history_restore. The only hint is contextual, from the sibling names, which the definition does not lean on.

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