ugf_set_token

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

Discloses restoring a cached token, implying non-destructive but doesn't state if it overwrites existing token. No annotations, but simplicity mitigates gaps.

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?

Two sentences, no fluff, front-loaded with action and purpose. Every word earns its place.

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?

Adequate for a simple set operation with one required parameter. Lacks mention of output or error conditions, but no output schema exists.

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 coverage is 100% and already describes the JWT parameter as 'Cached JWT from a previous ugf_authenticate call'. Description adds minimal extra meaning beyond that.

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 action ('restore') and resource ('cached UGF JWT'), and distinguishes from sibling ugf_authenticate by mentioning skip re-signing.

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 use on subsequent sessions to skip re-signing, implying when to use and when not (use ugf_authenticate for initial signing).

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