Hide Layer

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

The description discloses that entities become invisible but remain in regeneration, which is important behavioral context. With no annotations beyond the title, this provides good transparency, though it could mention if the change is permanent.

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 with no wasted words. The key purpose and side effect (invisible but still processed) are 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?

Given the tool's simplicity (one required parameter, no nested objects, output schema exists), the description is fully adequate for an agent to use it correctly.

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?

Only one parameter 'name' with schema description 'Layer name to turn off'. The description adds no further meaning beyond the schema, and schema coverage is 100%, so 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?

Description clearly states the verb 'turn off' and resource 'layer', with a key distinction that entities are invisible but still processed in regeneration. This differentiates it from sibling tools like layer_freeze which freezes layers.

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 explicit when or when-not guidance. The description is clear enough for a simple tool, but doesn't address alternatives like layer_show or layer_freeze, leaving the agent to infer from sibling names.

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