create_frame

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the creation action, without mentioning side effects, error conditions, required permissions, or what happens to the frame after creation. No context is given about auto-layout behavior or return values.

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 with no extraneous words, making it efficient and front-loaded. However, given the tool's 20-parameter complexity, it is slightly under-specified but still appropriately concise for stating the core purpose.

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 no output schema and no annotations, the description fails to provide necessary contextual details such as whether the tool returns the new frame's ID, requires a parent, or how the extensive parameters interact. For a complex creation tool with this many options, the one-sentence description is insufficient.

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?

All 20 parameters have detailed descriptions in the input schema, including notes like itemSpacing being ignored when primaryAxisAlignItems is SPACE_BETWEEN. The description adds no additional parameter information, so the baseline of 3 applies given the high schema coverage.

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 'Create' and resource 'frame', clearly stating the tool's function. It distinguishes from siblings like create_rectangle and create_text by the object type, though it doesn't elaborate on the unique characteristics of frames.

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 no guidance on when to use this tool versus alternatives like create_rectangle or create_text, nor does it mention prerequisites such as requiring a parent node. The phrase 'Create a new frame in Figma' offers no contextual usage information.

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