figma_set_flow_starting_point

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

The description discloses the API fallback mechanism and data storage via pluginData, explaining the shape of FlowStartingPoint. However, it does not fully explain behavioral effects of the 'replace' parameter (e.g., whether it overwrites other starting points).

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?

Two well-structured sentences: first states purpose clearly, second explains implementation details. No redundancy or excess.

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 purpose and data storage but lacks details on error conditions, prerequisites (e.g., must be a FRAME), and interaction with other flow starting points.

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 covers 75% of parameters with descriptions, but the description parameter is ambiguous: the tool description says stored data is only {nodeId, name}, yet the schema includes a description parameter. This creates confusion.

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 that the tool marks a FRAME as a prototype flow starting point, specifying the exact resource and action. It distinguishes from siblings like figma_create_prototype_connection which deals with connections.

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 usage for setting starting points but does not explicitly state when to use or not use this tool versus alternatives like setting connections. No exclusions or context provided.

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