revert_last_update

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

With no annotations, the description fails to disclose key behavioral traits such as whether the operation is destructive, whether it is reversible, what permissions are needed, or what constitutes a 'before-state'. The term 'revert' implies modification, but details are missing.

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?

The description is a single short sentence, which is concise and front-loaded. However, it could be slightly more structured (e.g., bullet points) without sacrificing brevity, but it remains informative for its length.

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?

Given no output schema, no annotations, and poor parameter descriptions, the tool definition is incomplete. An agent lacks critical information such as the definition of 'before-state', post-revert behavior, and error scenarios, which are essential for a revert operation.

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 provides no additional meaning beyond the input schema. Schema field descriptions are tautological (e.g., 'envId' and 'flowId'), and the description does not explain the purpose or origin of these identifiers, making parameter semantics insufficient.

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 clearly states the action ('Revert'), the resource ('selected flow target'), and the target state ('last recorded before-state'). This is specific and distinct from siblings like 'get_last_update' (retrieval) or 'apply_flow_update' (modification), so purpose is unambiguous.

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 guidance is provided on when to use this tool versus alternatives like 'preview_flow_update' or 'apply_flow_update'. There is no mention of prerequisites, context, or when not to use it, leaving the agent to infer usage.

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