set_item_spacing

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic action and does not mention side effects (e.g., that it modifies the frame's properties), conditions (e.g., only works on auto-layout frames), or restrictions beyond what the schema provides.

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 sentence with no redundant words. It is front-loaded with the verb and resource, making it quick to parse.

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?

The description does not mention the return value, confirm the side effects of modification, or explain the counterAxisSpacing parameter. For a tool with three parameters and no output schema, the description is too brief to be contextually 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 description coverage is 100% for all three parameters, so the baseline is 3. The tool description adds no extra meaning beyond the schema, such as explaining the interplay between itemSpacing and counterAxisSpacing or the condition about SPACE_BETWEEN.

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 uses the specific verb 'Set' and identifies the resource as 'distance between children in an auto-layout frame'. This clearly distinguishes the tool from siblings like set_padding, set_axis_align, and set_layout_mode, which operate on different aspects of layout.

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 lacks any guidance on when to use this tool versus alternatives. No mention of prerequisites, when not to use it, or comparison to sibling tools like set_padding or set_layout_sizing.

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