brand_extract_figma

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

No annotations provided, but description explains two modes, input formats, and that Figma values override web extraction. It is read-only in nature; however, it does not explicitly state non-destructiveness or side effects. Still, the behavioral context is strong.

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?

Compact single paragraph covering purpose, input formats, phases, and exclusions. No redundant sentences; every sentence adds value. Front-loaded with core purpose.

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?

Thoroughly covers complex tool with 8 parameters and two modes. Explains workflow, source priority, and relationship to other tools. No output schema, but description is complete for agent invocation.

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 has 100% coverage with descriptions, but the description adds rich context: origin of each input (e.g., variable_map from get_variable_defs, design_context from get_design_context), explanation of mode values, and purpose of figma_url. This goes beyond the 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?

Clearly states 'Extract brand identity from a Figma design file', lists multiple input formats, and explicitly distinguishes from sibling 'brand_extract_web' by stating 'NOT for web extraction (use brand_extract_web)'.

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 use (Figma extraction) and when not (web extraction, point to alternative). Describes two phases (plan and ingest) and source priority, giving clear usage guidance.

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