Set Layer Flags

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

The description discloses that only explicitly passed fields are modified and omitted flags retain their value, which is helpful. It also notes that returned flags reflect post-update state. However, it lacks details on error handling or side effects.

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 sentences, no fluff, front-loaded with key information. Every sentence adds value.

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 12 parameters and no output schema or annotations, the description is too brief. It omits details on error conditions, default values, and the relationship to other tools like 'set_params'.

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?

With only 17% schema description coverage, the description adds some value by explaining the partial update behavior, but it does not elaborate on individual boolean flags beyond 'visibility / render / lock'. The color parameter has schema description already.

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 states the tool toggles layer flags like visibility, render, and lock, which is clear. However, it does not explicitly distinguish it from sibling tools like 'set_params' that could also modify layer properties.

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 this tool versus alternatives (e.g., individual property setters or 'set_params'). The description implies it is for toggling multiple flags at once, but does not state this explicitly.

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