set_auto_layout

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the tool is a non-destructive write. The description adds value by explaining that the tool modifies auto layout settings and returns { ok, nodeId }. It details behavior per mode, going beyond annotations.

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 two sentences: first states purpose, second explains modes and parameters with returns. No fluff, every word earns its place. Highly efficient.

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 14 parameters, no output schema, and no param descriptions, the description covers the core logic and parameter grouping. It lacks details on optionality and exact parameter names but provides a solid high-level understanding. Could mention that nodeId and layoutMode are required.

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 0% schema description coverage, the description must compensate. It groups parameters by mode (e.g., 'padding / itemSpacing / alignment / wrap' for flex; 'gridRowCount / gridColumnCount / gridRowGap / gridColumnGap' for grid), adding semantic meaning. It does not individually document all 14 parameters but provides sufficient context.

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 tool's purpose: 'Configure a frame's auto layout.' It then details the three layout modes (NONE, HORIZONTAL/VERTICAL, GRID) and the parameters associated with each, distinguishing it from sibling tools like set_layout_props which handle other layout 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 provides context on when to use each mode: NONE disables, HORIZONTAL/VERTICAL enable flex, GRID enables CSS-grid. It does not explicitly state when not to use this tool or mention alternatives, but the mode-specific guidance gives clear usage context.

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