Lock Layer

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

The description discloses the main behavioral trait (entities visible but non-interactive). Since annotations lack readOnlyHint/destructiveHint, the description carries the burden and handles it well. It does not mention reversibility or permissions, but for a lock operation this is acceptable.

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?

A single, concise sentence that contains all necessary information. No fluff or redundancy.

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 state-changing tool with one parameter, the description covers the core effect. However, given the many layer siblings, a brief note about when to use lock versus freeze or hide would improve completeness.

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 coverage is 100% with a clear description for the 'name' parameter. The tool description adds no extra meaning beyond repeating the parameter's purpose, so a baseline score of 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?

The description clearly states the action (lock) and the resource (layer), and explains the effect: entities remain visible but cannot be selected or modified. This distinguishes it from layer_freeze (which hides) or layer_hide (which also affects visibility).

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?

No guidelines are provided on when to use this tool versus alternatives like layer_freeze, layer_hide, or layer_unlock. The description does not mention use cases, preconditions, or related tools.

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