set_marked_frames_locked

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

Annotations already declare readOnly=false, destructive=true, and idempotent=true, so the safety profile is covered. The description adds the return payload shape and hints that the asset is persisted via a 'saved' field, but it doesn't explain what 'locked' restricts or any permission/side-effect nuance, so value beyond annotations is modest.

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?

Two tight segments: the action sentence first, then the return shape. No filler, no repetition, and the key fact is front-loaded.

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?

With no output schema in structured data, the description supplies the return contract, and the two required params are covered by the schema. For a simple two-param mutation this is nearly complete, lacking only side-effect or failure-mode context.

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 both parameters (sequence_name, locked) are fully documented in the schema. The description adds no extra meaning such as accepted name format or how the locked flag interacts with existing keys, so the baseline 3 applies.

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?

States a specific verb (sets) applied to a precise resource and attribute (a Level Sequence's user marked frames' locked state). The scope is unambiguous and distinguishable from unrelated set_* tools, though it doesn't explicitly name its closest siblings like set_section_locked or set_playback_range_locked.

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 guidance about when to use this tool versus alternatives such as set_section_locked or the unlocked default, nor any prerequisites (e.g. that the sequence must exist or be loaded). Usage is only implied by the verb.

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