Refresh Access Token

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

The description says it automatically sets the new access token, indicating a mutation. Annotations only provide destructiveHint false. It does not detail side effects like token invalidation or permission requirements, but for a refresh operation the behavior is typical.

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, 12 words, no wasted text. Front-loaded and efficient.

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 simple token refresh with one parameter and no output schema, the description is complete enough. It could mention typical usage context (e.g., after login) but is adequate.

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 schema covers the parameter fully (100%). The description adds no extra meaning beyond what is in the schema's parameter description.

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 action: refresh the access token using a refresh token, and it automatically sets the new access token. It is distinct from login and logout siblings.

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 when a refresh token is available and a new access token is needed. It does not explicitly state when not to use it or mention alternatives, but it is clear for a simple token refresh.

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