rollback_policy_bundle

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 disclose the key behavioral trait: optimistic concurrency protection, which explains why expected_revision must match. However, it omits whether the rollback is reversible, what permissions it needs, and what happens on a revision mismatch, which matter for a mutation of this kind.

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 well-formed sentence with the action and its concurrency constraint front-loaded and no redundant clauses. The trailing '(Langflow 1.12.x)' version qualifier is a useful applicability note but reads as an afterthought rather than earning a place in the sentence.

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 three-parameter mutation with no annotations and no output schema, the description covers the core action and the concurrency requirement, which is the most important thing. It still leaves gaps around reversibility, side effects on currently running flows, and error behavior when expected_revision does not match.

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 100%, so revision, expected_revision, and reason are already documented in the schema. The description reinforces the concurrency meaning of expected_revision but adds no syntax, range, or format detail beyond what the structured fields provide — baseline 3.

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 a specific verb (roll back) and resource (policy bundle) and states the target (a prior revision), so the action is unambiguous. It does not explicitly distinguish itself from siblings like replace_policy_bundle or list_policy_bundle_history, but the 'roll back to a prior revision' framing is distinct enough to route an agent.

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 when-to-use guidance and no mention of alternatives, such as listing history first to find a valid revision or using replace_policy_bundle to move forward. The only implied usage comes from the required revision/expected_revision fields, which the agent must infer from the schema rather than the prose.

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