lock_decision_flow_revision

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

The description conveys that the tool makes the state immutable and creates a snapshot, which is a key behavioral trait not fully captured by the annotations. It doesn't mention reversibility or idempotency, but the term 'immutable' implies a non-reversible freeze.

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 two sentences, no redundancy, and directly conveys the purpose and usage. It is efficiently structured with a clear action statement followed by a contextual instruction.

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 simple tool with one parameter, the description is complete: it explains what it does, when to use it, and how it relates to the publishing step. The existence of an output schema (not shown) suggests return details are handled elsewhere, so no gap is apparent.

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 sole parameter decision_id is already well-documented in the schema (UUID, not name, with reference to list_decision_flows). The tool description adds no further semantic detail beyond what the schema provides, so the baseline of 3 is appropriate.

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 tool's action (lock), the object (decision flow), and the result (immutable revision). It is distinct from sibling tools like create, update, or publish by focusing on freezing a state.

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?

It explicitly says to call after a successful create/update, and explains the purpose of creating a point-in-time snapshot for later publishing. This gives a clear when-to-use context without ambiguity.

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