figma_get_design_system_summary

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

Annotations already mark readOnlyHint=true. Description adds that it is 'compact' and 'minimal tokens', which informs agent behavior. No contradictions. Could mention error cases or rate limits, but sufficient for a read-only tool.

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?

Description is concise (around 50 words) and front-loaded with key action. Includes pre-flight and a negative usage case. Every sentence adds value, though formatting could be slightly more structured.

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?

Covers purpose, parameters, and usage guidance. Lacks explicit return format or effect description, but for a minimal read-only overview with no output schema, it is reasonably complete given low complexity.

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 50% (limit and currentPageOnly lack schema descriptions). Description clarifies fileKey and figmaUrl usage ('target a specific file'), but does not explain limit or currentPageOnly parameters, leaving gaps.

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?

Description clearly states it provides a compact overview with specific content (variable collection names and component counts). Distinguishes from sibling tools by being a summary rather than detailed variable/component retrieval.

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 says when to target a specific file via fileKey/figmaUrl, and gives pre-flight instructions including reading specific files before calling. Also explicitly states when NOT to call (if DS identity known, use cache instead of empty target file).

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