refresh_all_tokens_tool

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

With no annotations, the description carries the full burden of behavioral disclosure. It says tokens are refreshed for ALL shops but never mentions side effects (e.g., invalidating existing tokens), required permissions, rate limits, or whether the operation is reversible or idempotent. For a mutation-like tool, 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?

Two short sentences, front-loaded with the core action and scope, followed by a targeted use case. Every sentence earns its place with no filler.

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 tool is simple, but with no annotations, an undocumented and seemingly arbitrary parameter, and no mention of auth or side effects, the description is incomplete. The output schema covers return values, but the description fails to address key invocation context for a batch token refresh.

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?

Schema description coverage is 0% and the single parameter 'random_string' is undocumented in both schema and description. The description does not explain what this parameter does or whether it affects behavior, leaving the parameter semantics completely opaque.

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 states a specific verb (refresh) and resource (access tokens) with an explicit scope (ALL configured shops), which distinguishes it from the singular sibling refresh_token_tool. However, it does not explicitly name that sibling, so a perfect 5 requires the agent to infer the contrast from the word ALL.

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?

'Useful for batch renewal before expiry' gives a clear use case (batch renewal before token expiry), but it does not state when to use the singular refresh_token_tool instead or any exclusions. The guidance is implied rather than explicit.

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