set_layer_visibility

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

No annotations are provided, so the description must carry the full burden. It does not disclose potential side effects, such as whether setting visibility is reversible or requires specific permissions. The description is minimal.

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 short but redundantly lists parameters in an args block that mirrors the schema. It could be more concise by omitting the schema duplication while retaining the core explanation.

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 setter tool, the description is adequate but not fully complete. It covers the basic purpose and parameters but lacks behavioral details and usage guidance, given the absence of annotations and output schema.

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%, meaning the description must add value. However, it only lists parameter names and types, which are already in the schema. It does not explain the effect of 'visible' (e.g., default true), valid values, or any constraints.

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 'Set layer visibility by name,' specifying the verb (set) and the resource (layer visibility). It distinguishes itself from siblings like set_layer_blend_mode or set_layer_opacity.

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., set_layer, set_layer_blend_mode) is provided. The description does not mention prerequisites or context such as requiring the file to be open.

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