max_set_layer_hidden

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

With no annotations, the description must carry the behavioral burden; 'Undoable' is a genuinely useful disclosure about reversibility. However, it doesn't say what happens on an unknown layer name (error vs no-op) or any permission requirements, leaving key mutation behavior unstated.

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?

Two short sentences with zero waste; the primary action and its parameter mapping are front-loaded before the undo note.

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?

An output schema exists so return values needn't be covered, and the description does explain the toggle and its undoability. The remaining gap is edge-case behavior (invalid name) for an otherwise simple two-parameter mutation.

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 0%, so the description must compensate. It does clarify the meaning of the 'hidden' boolean (True=hide, False=show), which adds real value, but 'name' semantics (exact match, case sensitivity, path vs leaf) are left entirely unexplained.

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?

States a specific verb and resource ('Hide... or show... a layer by name') and even disambiguates the boolean mapping inline (hidden=True/False). An agent can distinguish this from siblings like max_layers (listing) or max_selection without opening the schema.

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 toggle semantics are spelled out, which implies when to use it, but there is no explicit guidance on when to prefer this over alternatives or any preconditions. Usage is implied rather than stated.

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