set_item_spacing

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

Description discloses behavioral quirks: itemSpacing is ignored if primaryAxisAlignItems is SPACE_BETWEEN, and counterAxisSpacing works only with layoutWrap set to WRAP. This goes beyond the input schema.

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?

Single sentence clearly states purpose with no unnecessary words; highly concise.

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?

Adequate for a simple setter tool, but lacks mention of return values, error handling (e.g., invalid nodeId), or requirement that node be auto-layout. No output schema, so description could be more complete.

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 100%, but description adds value by explaining the conditions under which parameters are effective (e.g., ignored values), which is not captured in schema descriptions.

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?

Description uses specific verb 'set' and resource 'distance between children' in the context of 'auto-layout frame', clearly distinguishing it from sibling tools like set_padding and set_layout_mode.

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?

Description implies usage for auto-layout frames but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it (e.g., if the frame is not auto-layout).

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