set_padding

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

No annotations are provided, so the description must disclose behavioral traits. It simply states 'Set padding values' without mentioning that the frame must already be an auto-layout frame, that individual side padding may require independent padding mode, or any constraints on values. This leaves significant behavioral gaps.

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, clearly front-loaded with 'Set padding values.' It contains no superfluous content, though 'in Figma' is arguably redundant, but it remains concise and to the point.

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?

With 5 parameters, no annotations, and no output schema, the description should provide more context about usage constraints and side effects. It omits the auto-layout prerequisite and independent padding behavior, making it insufficient for reliable agent 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 coverage is 100%, with each parameter already described as 'Top padding value' etc. The description adds no additional parameter-level meaning beyond restating 'padding values.' Baseline 3 applies as the schema does the heavy lifting.

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 a specific verb 'Set' and resource 'padding values', with context 'auto-layout frame', distinguishing it from siblings like set_item_spacing and set_layout_mode. It clearly states the tool's function.

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 phrase 'auto-layout frame' implies a precondition, but the description does not explicitly state when to use this tool versus alternatives like set_item_spacing or set_layout_mode. No exclusions or alternative recommendations are provided, making usage guidance merely implied.

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