Refreshes the long-lived OAuth token for this agent workspace
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "oauth_refresh"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| query | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. It mentions that the token is long-lived and scoped to this agent workspace, but it does not disclose side effects, whether the old token is invalidated, authentication requirements, rate limits, or what the tool returns.
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 a single front-loaded sentence with no wasted wording. It is clear and compact, though its brevity reflects under-specification rather than complete economy.
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 credential-mutating OAuth refresh tool with no annotations, no output schema, and an undocumented parameter, the description is too sparse. It states the purpose but omits essential context such as return behavior, safety implications, and parameter meaning.
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 one optional parameter named 'query' with 0% description coverage, and the description does not mention it at all. An agent has no guidance on what 'query' means for an OAuth refresh operation or what value to supply.
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 gives a specific verb and resource: 'Refreshes the long-lived OAuth token for this agent workspace.' It clearly identifies the operation. However, it does not distinguish this from nearby credential or token tools such as token_vault or credential_broker, so sibling differentiation is missing.
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?
There is no explicit guidance on when to use this tool, when not to use it, or which alternative to choose. The purpose implies it is for token refresh, but the description gives no conditions, prerequisites, or comparison to sibling token/credential tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.