set_layout_mode

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

The description only says 'Set the layout mode and wrap behavior,' but does not disclose any behavioral implications (e.g., whether the frame must have auto-layout enabled, if changes are reversible, or any required permissions). With no annotations, the description should carry this burden.

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, clear sentence that front-loads the action and resource. No unnecessary words exist; it is appropriately sized for the tool's complexity.

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 mutation tool with 3 parameters and no output schema, the description covers the basic purpose but lacks details on constraints (e.g., valid node types, interaction with other layout properties) and expected behavior. It is minimally viable.

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?

The schema already provides full descriptions for all three parameters (100% coverage), so the description adds only a generic restatement of 'layout mode and wrap behavior.' It does not clarify value meanings or usage beyond the enum definitions.

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 verb 'Set' and the resource 'layout mode and wrap behavior of a frame'. It clearly identifies the specific functionality and distinguishes from sibling tools like set_layout_sizing or set_padding.

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 is provided on when to use this tool versus alternatives, nor any when-not-to-use conditions. The description simply states the action without context for selection.

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