Show Layer

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

The description correctly indicates a state change (turning on a layer), which is appropriate for a mutation tool. No annotations provide additional attributes, so the description is adequate but does not elaborate on side effects or response.

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 sentence with no unnecessary words, efficiently conveying the tool's purpose.

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 toggle tool, the description is mostly complete. However, it lacks usage context regarding the layer's current state (e.g., if already on) or prerequisites, but this is minor given the 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 only parameter 'name' is already described in the schema as 'Layer name to turn on'. The description adds no extra meaning beyond that, so baseline 3 is appropriate given 100% schema coverage.

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 (turn on) and the resource (layer), and it distinguishes this from sibling tools like layer_hide (which turns off) by specifying 'previously turned off'.

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 is provided on when to use this tool versus alternatives like layer_thaw (for frozen layers) or layer_unlock. The description simply states what it does without context.

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