figma_get_design_context

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

Disclosures caching behavior (60s per session) and safe defaults. The debug parameter to bypass cache is mentioned. Annotations (readOnlyHint) are consistent. No contradictions.

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 concise sentences: purpose, defaults/safety, and explicit overrides + caching. Front-loaded with no wasted words.

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 12 parameters and no output schema, the description covers core purpose and key defaults but omits details on many optional parameters and the structure of the response. Incomplete for a full understanding.

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 low (33%). Description adds meaning for depth, verbosity, and caching, but many parameters (includeLayout, includeVisual, includeTypography, includeCodeReady, outputHint) remain unexplained. This partially compensates but not fully.

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 retrieves design context including structure, text, layout, visual, and typography for a node or whole file. It distinguishes from siblings specializing in specific data like components or file data.

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?

Provides guidance on default depth and verbosity for context safety, and recommends explicit overrides for deeper data. Caching info is also given. However, it lacks explicit when-not-to-use or alternatives among siblings.

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