Обновление сессии

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

The description goes beyond the annotations by revealing the exact fallback chain: refresh_token first, silent SSO_SESSION re-login on invalid_grant, and REAUTH_REQUIRED if both paths fail. This is valuable behavioral context, especially the fact that no OTP prompt is involved.

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?

The description is short, clear, and front-loaded with the core purpose. Every sentence adds necessary information: the action, the primary mechanism, the fallback mechanism, and the terminal failure condition. No filler or repetition.

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 zero-parameter tool with a known output schema, the description covers everything needed to invoke it correctly: what it does, how it handles failures, and what final state the agent should expect. The mention of REAUTH_REQUIRED is particularly useful for the calling agent.

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 formal parameters and the input schema is already complete at 100% coverage. The description correctly explains the internal refresh behavior without needing to document parameters. This matches the baseline for parameter-light tools.

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 identifies the action: refresh a session, with a specific object and a concrete inner fallback flow. It stands out from generic 'login' or 'status' sibling tools, but it does not explicitly name the alternatives it differs from, so it stops just short of a 5.

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 use case is implied: an agent should call this to refresh an existing session, first by refresh_token and then by silent SSO re-login when invalid_grant occurs. However, the description does not explicitly say when to call this instead of `keepalive`, `session_status`, or `login`, nor does it mention conditions like an expired token.

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