pull_design_system_rest

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

Discloses error behavior for missing env vars, 403, and 404. States success return format. With no annotations, covers key aspects but could mention rate limits or idempotency.

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?

Reasonably concise with clear sections. Minor repetition of 'no plugin or Figma Desktop required' but overall efficient and front-loaded.

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?

Comprehensive for a zero-parameter tool: explains return format, error behavior, prerequisites, and usage context. No output schema needed, description suffices.

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?

No parameters, so baseline is 4. Description does not need to add param info. Schema coverage is 100%.

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 'Pull the design system from Figma via REST API', using a specific verb and resource. It distinguishes from sibling tools like 'pull_design_system' and 'get_tokens' by emphasizing no plugin or bridge needed.

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 provides when to use: 'when the Figma plugin is not available (CI, headless, remote) or when you want to pull tokens without starting the bridge.' Also lists prerequisites and gives equivalent CLI command.

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