Set the Sedis session token (after re-proving 2FA)

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

Discloses important behavioral traits beyond the sparse annotations: the token is cached locally (owner-only file), sent as the X-Api-Session header on every subsequent call, and never logged or echoed. This provides critical context about statefulness and privacy.

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 concise sentences, each earning its place: the first states the core action and benefit, the second gives the trigger and workflow, the third explains side effects. Front-loaded and free of 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?

For a single-parameter setter with no output schema, the description fully covers the trigger condition, the exact steps to obtain the token, what the tool does with it, and post-call behavior. Nothing critical is missing.

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 the parameter description already includes the example prefix and workflow. The tool description reinforces these but also adds behavioral context about caching and header usage, enriching the parameter's purpose beyond the schema alone.

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 tool's function: pasting a session token to refresh the session without restarting. It distinguishes itself from the sibling 'clear_session' by being the setter counterpart, and the title adds the specific context of 'after re-proving 2FA'.

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 instructs when to use: when a tool returns 'Session re-verification required'. Provides a concrete step-by-step workflow (open reproveUrl, complete 2FA, copy token, call this tool, retry original call), eliminating ambiguity.

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