create_frame

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

No annotations are provided, and the description fails to disclose behavioral traits beyond the basic creation action. It does not mention side effects, authentication requirements, or what happens to existing elements. With a mutation tool, this is a significant gap.

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 extremely concise but at the cost of completeness. It fits in one sentence, but it does not front-load critical information or provide a structured overview. It is not wasteful, but it is under-informative.

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 the tool's complexity (20 parameters, nested objects, many enums) and no output schema, the description is vastly inadequate. It does not explain return values, behavior in edge cases, or interactions with other tools. The single sentence fails to cover essential context.

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?

The input schema has 100% coverage, so the baseline is 3. The description adds no additional meaning beyond the schema; it merely repeats the action. While the schema's parameter descriptions are detailed, the tool description does not improve understanding.

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 'Create a new frame in Figma' clearly identifies the verb and resource, but it does not distinguish this tool from sibling tools like create_rectangle or create_text, which also create nodes. A more specific description would mention that frames are containers for other elements.

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. For instance, it does not explain when a frame is preferable to a rectangle or text node, nor does it mention any prerequisites or context (e.g., requiring a parent node).

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