pull_design_system_rest

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

Describes return format on success and detailed error behavior for missing env vars or specific API errors (403, 404). Although no annotations are provided, the description covers key behavioral traits without contradiction.

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 very concise, using two short paragraphs with bullet-style points that front-load the main purpose. Every sentence adds unique value without redundancy.

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?

Given zero parameters and no output schema, the description fully covers prerequisites, success/error responses, and usage guidance. It is complete for an agent to correctly invoke the 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?

The tool has zero parameters and schema coverage is 100%, so no parameter documentation is needed. The description appropriately focuses on other aspects.

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 verb 'Pull', the resource 'design system from Figma via REST API', and distinguishes from the likely sibling 'pull_design_system' by noting 'no plugin or Figma Desktop required' and equivalence to 'memi pull --rest'.

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 prerequisites (FIGMA_TOKEN, FIGMA_FILE_KEY) and states when to use this tool: 'when the Figma plugin is not available (CI, headless, remote)' or 'without starting the bridge', effectively differentiating from sibling tools.

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