figma_enumerate_published_components

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

Annotations indicate readOnlyHint=true and destructiveHint=false. The description adds valuable context: response shape is compact by default, descriptions stripped to keep <10KB, and large libraries (1000+) require filter to avoid overflow. 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?

Single paragraph, front-loaded with purpose, no wasted words. Every sentence adds value. Efficient and clear.

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?

Despite no output schema, the description explains response shape and version (v3.4+). Covers all key aspects: purpose, usage, parameters, limitations. Very complete for this 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 coverage is 100% with decent descriptions. The description adds extra meaning: explains limit hard cap (500), filter's substring nature, libraryFileKey extraction, and includeDescription warning about length. Adds value beyond schema.

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 uses a specific verb ('List') and resource ('published COMPONENT + COMPONENT_SET of a library via the Figma REST API'), clearly distinguishing it from siblings like figma_enumerate_library_components. It also notes the tool works without the library file being open.

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?

Explicitly states when to use: when library is subscribed but tabs aren't open. Mentions prerequisite (figma_set_rest_token) and gives guidance for large libraries (use filter). Lacks explicit alternatives but still clear.

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