refresh_token

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

No annotations are provided, so the description carries the full burden. It mentions 'use a valid token' but does not explain whether an Authorization header is required, what invalidates the old token, whether the response returns a new access token or expires the prior one, or any rate limits or auth prerequisites. For a security-sensitive auth endpoint this is a significant gap.

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 bloated with a redundant keyword list ('refresh_token, refresh token, refresh auth, get auth, fetch auth, read auth...') that repeats the name and title many times over. The valuable content ('Use a valid token to get another token') is a single sentence buried after the endpoint note and before the keyword noise.

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?

No output schema, no annotations, and a bare endpoint URL leave key details missing: how the token is supplied, what the response contains, and what happens to the old token. For an auth refresh endpoint the definition is under-specified.

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 has zero parameters, so the baseline is 4. The description correctly implies no body parameters are needed ('use a valid token'), though the mechanism of passing that token is unstated.

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?

States the resource (token) and the action (refresh), but the phrasing 'Refresh auth' and 'Use a valid token to get another token' restates the name rather than explaining the operation. It is not clearly distinguished from siblings like get_token or oauth_login that also mint tokens.

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?

No guidance on when to use this versus get_token, oauth_login, or create_api_token. The keyword dump does not substitute for actual when/when-not instructions, leaving the agent to guess among several token-related siblings.

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