production.character_lock_regions

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

The description adds useful behavioral context beyond annotations: roles change, regions are recaptured, and low-confidence regions cannot become editable, yielding REGION_AMBIGUOUS. However, it remains unclear what mutation is actually performed on the mesh, what permissions or ordering constraints apply, and what reversibility means for a non-idempotent write tool.

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 short and has no wasted filler, but it is not front-loaded with a clear purpose statement. The phrasing is cryptic enough that brevity comes at the cost of comprehensibility.

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?

The output schema exists, so return values need not be explained, but the description still does not provide enough context for a complex eight-parameter mutation tool. Usage, parameter meaning, and side-effect detail remain largely absent.

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 explain the eight parameters, but it does not. It vaguely references a manifest and the concept of editability, yet lock, unassign, intentional, object_name, tolerance_m, and operation_id remain completely unexplained.

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 refers to a new manifest with changed roles and recaptured regions, but it never plainly states that the tool locks or changes region roles. An agent must infer the core action from the tool name rather than from a clear verb-resource statement.

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 explicit when-to-use guidance, no prerequisites, and no comparison to siblings such as character_validate_locked_regions or character_define_regions. The REGION_AMBIGUOUS note is a constraint, not routing guidance.

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