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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered structurally. 'Safe to repeat' merely restates idempotentHint; the one genuine addition is blast radius ('every account on the profile'), which tells the agent this is not a per-account operation. It still omits what happens to old tokens and whether users must re-authorize.

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, zero padding, with the operation and its scope front-loaded before the safety note. Nothing could be trimmed without losing content.

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?

A single-parameter, annotation-rich tool with no output schema doesn't need much, and the description covers what happens and to whom. It falls short only on failure modes and rate-limit/cadence expectations, which are minor here.

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?

Only one parameter and schema description coverage is 100% ('A profileId from list_profiles'), so the schema fully documents the input. The description's phrase 'on the profile' loosely implies profileId but adds no format, sourcing, or constraint detail beyond what the schema already states.

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 a specific verb (refresh) and resource (provider tokens for every account on a profile), with scope made explicit. No sibling tool performs token refresh, so no disambiguation is needed, but the description also doesn't explicitly rule out nearby concepts like reconnecting an account.

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 indication of when to call this — e.g., after expired credentials, after connecting accounts, or scheduled maintenance — and no mention of prerequisites such as the profile needing existing accounts. 'Safe to repeat' hints at retry behavior but is not usage guidance in the when-to-use sense.

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