set_layer_lock

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

Description states lock/unlock effect but no annotations provided. Lacks details on side effects, permissions, or what 'against edits' means in practice (e.g., can the layer still be selected?). Minimal behavioral disclosure.

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?

Single sentence is concise but under-specified. No wasted words, but lacks structure or additional context that would aid understanding without being verbose.

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?

Given low complexity (3 params, no output schema), the description should explain more. Lacks return value info, clarification on boolean locked, and integration with sibling tools. Insufficient for correct agent 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 coverage is 33% (only doc_id described). Description adds no parameter meaning beyond schema; e.g., 'locked' parameter not clarified (true=locked? false=unlocked?). Does not compensate for missing schema descriptions.

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?

Description clearly states it locks or unlocks a layer against edits, with specific verb and resource. Distinguishes from siblings like set_layer_visibility (visibility) and set_active_layer (active layer).

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 guidance on when to use vs. alternatives, no prerequisites or when-not-to-use. For example, does the layer need to exist? Should this be called only after adding a layer?

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