Call raw Figma REST API

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

With no annotations, the description must disclose behavioral traits. It only mentions using stored OAuth tokens and that it calls official APIs, but does not disclose potential side effects, error handling, rate limits, or that it can perform destructive operations. This is insufficient for a tool that can make arbitrary API calls.

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 that immediately conveys the core function without extraneous words. It is appropriately concise and front-loaded.

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 tool complexity (8 parameters, no output schema, no annotations), the description is too brief. It does not explain how to use operationId vs raw path, what the output format is, or how to construct requests. Significant gaps remain for an agent to correctly invoke the tool.

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 0%, and the description elaborates on none of the 8 parameters. It only hints at operationId and method/path but fails to explain body, query, userId, headers, pathParams, or their purposes. The description does not compensate for the lack of schema descriptions.

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 tool calls any official Figma REST API operation via operationId or raw method/path, which is specific and distinguishes it from tools like figma.call_api by mentioning both identification methods. However, it does not explicitly differentiate from the sibling figma.call_api, so it falls short of a 5.

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?

No guidance is provided on when to use this tool versus alternatives such as other sibling tools like figma.call_api or specific CRUD tools. The description lacks any contextual cues for appropriate use.

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