tldraw_lock_shapes

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

The description discloses that locked shapes cannot be selected or moved, which is the key behavioral effect. However, it does not mention other consequences (e.g., can they be deleted?), error scenarios (e.g., invalid shape IDs), or whether the operation is reversible.

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 extremely concise (one sentence) and front-loaded with the action and effect. Every word is necessary and no information is redundant.

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 lock/unlock operation, the description covers the purpose and behavioral effect. Minor gaps exist: no mention of error handling, idempotency, or return value, but these are not critical for this tool's simplicity.

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 input schema already provides clear descriptions for both parameters. The description adds no additional meaning beyond what the schema states, meeting the baseline expectation.

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 verb ('lock or unlock') and resource ('shapes'), and the UI effect distinguishes it from other shape modification tools like tldraw_move_shapes or tldraw_delete_shapes.

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 implies usage for locking shapes but does not provide explicit guidance on when to use vs alternatives, nor does it mention prerequisites or context (e.g., 'use this after creating shapes to prevent unintended edits').

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