Create via any figma.create* API

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

No annotations are provided, so the description carries the full burden. It only mentions creation and optional property setting/reparenting but lacks details on side effects, error handling, or safety. The tool is a mutation (create) but no further behavioral context is given.

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 waste, front-loading the core purpose. However, it could be more structured to separate the three steps (call, set properties, reparent). Still, it is appropriately sized for the complexity.

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 6 parameters, no output schema, and no annotations, the description is too minimal. It does not cover the pattern validation for createMethod, the structure of args, or the return value. An agent would need additional documentation to use this tool correctly.

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 0%, so the description must add significant meaning. It explains that createMethod specifies the method, properties sets node properties, and implies parentId is for reparenting. However, it does not explain args, index, or pageId, and the generic 'anyOf' schema is complex.

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 clearly states it calls any figma.create* method, then optionally sets properties and reparents, which is a specific verb and resource. It distinguishes from siblings by being a generic wrapper for any current or future create method.

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 implies when to use: when calling a create method that may have no dedicated tool, or when combining creation with property setting and reparenting. However, it does not explicitly mention when not to use it or suggest alternatives like the specific create tools.

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