get_token_storage_config

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

Discloses what is returned (storageType blob, metadata), what is NOT returned (credentials), and null case. Lacks explicit statement of read-only nature but no annotations to contradict.

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?

Three sentences with all essential information, front-loaded purpose, no 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?

Explains return structure and null case despite no output schema; pairs with sibling tool. Lacks detail on permissions or side effects, but adequate for 0-param 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?

No parameters in schema (100% coverage), description adds context that tool requires no input by stating 'auto-discovers' from the live file, going 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?

Clear verb 'auto-discover' and specific resource 'sync provider config from the live Figma file'. Distinguishes from sibling tools like 'get_token_catalog' by stating pairing and different purpose.

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 (auto-discover config) and when to pair with 'get_token_catalog'. Also explains null case and alternative approach for local cache.

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