figma_reset_slot

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the reset target state and multi-file execution constraints, but it does not state whether the reset is reversible, what permissions are required, or what happens if the slot does not exist.

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 front-loaded with the core action and then separates the multi-file caveat into a clearly marked second paragraph. It is efficient, though the multi-file note is somewhat verbose relative to the simple reset operation.

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?

The description covers the main operation and the non-obvious fileKey behavior, and the schema fully documents all parameters. However, without annotations or an output schema, it leaves gaps around mutation safety, error conditions, and when this tool should be preferred over related slot operations.

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 all four parameters are already documented in the input schema. The description reinforces fileKey behavior but does not add meaning beyond the schema for slotId, slotName, or instanceId, making the baseline score 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 states a specific verb and resource: reset a slot on a component instance to its default empty state from the main component. This clearly distinguishes the tool from siblings like figma_create_slot or figma_append_to_slot without needing to name them explicitly.

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?

Usage is only implied by the tool name and the first sentence. The description explains the fileKey mode condition but does not explicitly say when to choose reset versus append or create slot operations, nor does it list prerequisites or exclusions beyond Cloud Mode fileKey rejection.

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