refresh_all_sessions

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

With no annotations, the description must disclose behavioral traits. It mentions the action and return value but omits potential side effects such as whether existing sessions are invalidated, what happens on partial failure, or any auth requirements beyond 're-authenticate.' This is a significant gap for an operation affecting all sessions.

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, each earning its place: the first states the action, the second states the return. No padding 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?

The description is sufficient for a no-parameter tool with an output schema, but given the lack of annotations, it leaves questions about side effects and prerequisites unanswered. The output schema covers the return structure, but behavioral completeness is lacking.

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, so the description correctly refrains from parameter details. The schema already trivially covers parameters, and the baseline for 0 params is 4.

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 specifies the action ('Re-authenticate') and the exact scope ('every configured session'), clearly distinguishing from sibling tools like refresh_session, which handles a single session. The mention of a per-session report further clarifies the output.

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 provides clear context (bulk operation over all sessions) that implies when to use it, but it does not explicitly mention alternatives or exclusions. It falls short of a 5 because it doesn't say 'use this instead of refresh_session' or note any prerequisites.

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