set_scene_item_locked

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

With no annotations, the description carries the full transparency burden and clearly states the mutating behavior (lock or unlock). However, it does not disclose whether the operation overwrites the existing locked state, what happens for invalid scene/item IDs, or any side effects.

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 that is front-loaded and contains no filler or redundant information. It is maximally concise.

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?

While the tool is simple, the description is minimal for the context. It lacks any reference to the `get_scene_item_locked` counterpart, leaves parameter semantics unexplained, and provides no error or prerequisite context, making it insufficient for confident invocation.

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%, and the description does not explain the three required parameters. It only implies that a scene item is targeted, leaving `scene_name` and `scene_item_id` entirely to the schema titles, which is a significant gap.

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 uses a clear verb ('Lock or unlock') and a specific resource ('scene item'), so the core operation is obvious. It does not explicitly distinguish itself from sibling tools like `get_scene_item_locked`, but the verb signals a write operation.

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?

The description provides no guidance on when to use this tool versus alternatives, no mention of prerequisites, and does not reference the `get_scene_item_locked` sibling for reading the current locked state. It gives no context about selection or error handling.

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