figma_set_visible

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

With no annotations provided, the description carries the full burden of behavioral disclosure. However, 'Show or hide a node' merely restates the tool's name and the boolean parameter, without mentioning side effects, undo behavior, or impact on child nodes. It does not contradict annotations since none exist.

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 concise sentence with no wasted words. It is appropriately front-loaded and for a simple tool, brevity is acceptable. However, it is borderline under-specification, which keeps it from a 5.

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, the description is minimal but lacks critical context: no mention of the boolean semantics, how to target the node, or any behavioral expectations. With no annotations or output schema, and 0% parameter coverage, the description is insufficient for reliable invocation.

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 description coverage is 0%, so the description must compensate. It does not explain that 'visible' is a boolean controlling visibility, nor how 'nodeId' is specified (e.g., path, ID, selection). The parameter names are somewhat self-explanatory but lack explicit detail.

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 'Show or hide a node' uses a specific verb ('show/hide') and a clear resource ('node'), which precisely states the tool's function. It distinguishes itself from sibling tools like figma_set_opacity or figma_resize_node, which handle different 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?

The description gives no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. No context is provided about relationships to sibling tools such as figma_set_opacity or figma_set_fill.

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