getFigmaColorPalette

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

With no annotations provided, the description carries the full burden. It fails to explicitly state that this is a read-only operation without side effects, nor does it mention authentication requirements or error behavior. It only describes the output, leaving safety and side-effect assumptions to the agent.

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, front-loaded with the primary purpose, and every word adds value. It is appropriately sized for a simple tool with no unnecessary repetition.

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?

For a simple extraction tool with a sparse schema and no output schema, the description adequately covers what the tool does and what it returns. It could clarify whether the palette is for the whole file or a selection, but it is sufficient for basic usage.

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?

The schema covers 100% of the parameters (fileKey and figmaToken) with clear descriptions, so the description does not need to add extra parameter semantics. It adds no new parameter-level information, but the schema is sufficient.

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 ('Extract color palette') and describes the output (unique colors with hex, rgba, usage count). This distinguishes it from sibling tools like getFigmaStyles or getFigmaFrame, which have different purposes.

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?

Usage context is implied by the name and description—use this when needing color palette data from a Figma file—but no explicit guidance is given about when to prefer this over alternatives, nor are any exclusions or preconditions mentioned.

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