create_frame

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

With no annotations, the description held full responsibility for behavioral disclosure. It only states 'Create a new frame' with no mention of side effects, permissions, or return behavior. This is insufficient for a mutation tool, scoring 2.

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, concise and front-loaded. It is not verbose, but for a tool with 21 parameters, it may be too brief. However, it earns a 4 for being efficient without waste.

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 complexity (21 params, no output schema, no annotations), the description is incomplete. It omits return value, success conditions, and context about how it fits with sibling tools. A 2 reflects this inadequacy.

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%, so the schema fully documents parameters. The description adds no additional meaning beyond what the schema provides. Baseline 3 is appropriate.

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 the action and resource: 'Create a new frame in Figma'. However, it does not differentiate from sibling tools like create_rectangle or set_auto_layout, which also create or modify frames. A 4 indicates good clarity but lacks sibling differentiation.

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. No when-to-use, when-not-to-use, or context about prerequisites. This is a significant gap, earning a 2.

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