get_figma_file

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

Annotations already indicate a safe read-only operation. The description adds a behavioral warning about large payloads and suggests compact mode to mitigate this, which is useful context beyond the annotations. However, it does not disclose other behaviors like return format or versioning semantics.

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 two concise sentences that front-load the action and purpose. Every word contributes, with no redundancy or filler, achieving maximum clarity in minimal space.

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?

With no output schema, the description does not explain the return structure or contents beyond 'a Figma file.' Given the tool has 4 parameters and a warning about payload size, more context is needed about what the response includes, version handling, and parameter semantics.

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%, yet the description only minimally references 'compact mode' related to the responseMode enum. It does not explain fileKey, version, or debugTelemetry, leaving the agent to infer from parameter names alone. This insufficiently compensates 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 fetches a Figma file, using a specific verb and resource. It distinguishes from siblings like get_figma_nodes or get_figma_images by targeting the whole file, though it does not explicitly mention scope beyond 'a Figma file'.

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 like get_figma_nodes or get_figma_images. The advice to prefer compact mode is about parameter selection, not tool selection, and no exclusions or alternative tools are mentioned.

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