apply_token_remap

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

Discloses plugin requirement, dryRun behavior, and single undo entry for batch. Given no annotations, the description provides good behavioral context, though missing potential side effects like overwriting existing tokens.

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?

Three sentences: purpose, prerequisite, usage details. No unnecessary words. Front-loaded with key action.

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?

Covers plugin dependency, relationship with propose_token_remap, dryRun, and undo behavior. Lacks error handling or confirmation details, but adequate for nested-object tool with no output schema.

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?

Explains plan and dryRun parameters with context (plan from propose_token_remap, dryRun for validation). But planId parameter is not described, and schema coverage is 0% so description partially compensates.

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 ('Apply a remap plan'), the target ('live Figma file'), and the mechanism ('via the companion plugin'). It distinguishes from sibling tools like propose_token_remap and bridge_status.

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?

Explicitly mentions prerequisites (plugin running and connected) and recommends calling bridge_status first. Also instructs to pass plan from propose_token_remap with chosen decisions. No explicit when-not-to-use, but context is clear.

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