set_layout_mode

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

With no annotations provided, the description must fully disclose behavior. It mentions setting layout mode and wrap behavior, implying mutation, but does not explain potential side effects (e.g., what happens if layoutMode is NONE with layoutWrap set, or whether the frame must already have auto-layout). This is a significant gap for a mutation tool.

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, front-loaded sentence that directly conveys the tool's purpose with no wasted words. It is appropriately concise for a straightforward setter tool.

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 simple parameter set and no output schema, the description covers the basics. However, it omits important constraints like frame eligibility and behavior nuances between layout modes, leaving the agent to infer potentially critical context for correct 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 100%, so baseline is 3. The description's phrase 'wrap behavior' adds minimal clarification beyond the schema's own parameter descriptions but does not provide deeper semantics such as interactions between layoutMode and layoutWrap.

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 the specific verb 'set' and resource 'layout mode and wrap behavior of a frame', making it distinct from sibling tools like set_padding or set_layout_sizing. It unambiguously identifies what the tool does and what entity it operates on.

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 implies the tool should be used to set layout mode and wrap behavior, but provides no explicit guidance on when to use it over alternatives or any prerequisites such as the node needing to be a frame with auto-layout enabled. Lacks exclusions or alternative tool references.

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