set_access_token

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The term 'cache' is vague about persistence, overwrite behavior, or side effects. The description lacks details on what the tool does beyond storing the token, and does not mention error conditions or return value structure.

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?

A single sentence that is front-loaded and covers the essential purpose. Every word is justified, and there is no verbosity or 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?

An output schema exists, so return values do not need description. However, the tool lacks behavioral context (e.g., idempotency, error handling). Given the low complexity (one required parameter), the description is minimally adequate but leaves gaps in usage context.

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 description coverage is 0%, requiring the description to compensate. The description calls the token a 'freshly pasted scapi_access_token' but does not explain format, constraints, or how to obtain it. For a single parameter, more semantic guidance would be beneficial.

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 'cache' and the resource 'scapi_access_token', specifying its origin from the FSA-token bookmarklet. While it doesn't explicitly distinguish from siblings, the sibling tools are unrelated (cart, auth, etc.), making the purpose sufficiently clear.

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?

The description implies usage after pasting from a specific bookmarklet, but it does not explicitly state when to use this tool versus alternatives, nor does it provide any conditions or prerequisites. No explicit when-not or alternative guidance is given.

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