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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so 'Safe to repeat' largely restates structured data. The description does add one genuinely behavioral fact not covered by annotations: the mutation applies to every account on the profile, not a single account. It says nothing about partial-failure handling or whether existing tokens are invalidated.

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 filler, and the core action and scope are front-loaded before the repeatability note.

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 single-optional-parameter bulk mutation with full annotation coverage and no output schema, the description is adequate but thin: it omits what happens if refresh fails on some accounts and what the caller observes afterward. Annotations carry the safety profile, so the gap is moderate rather than severe.

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?

There is only one optional parameter and schema description coverage is 100%, with the schema itself explaining that profileId defaults to the key-bound profile. The description adds no additional meaning about the parameter, which is the expected baseline when the schema does the work.

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 of every account on the profile), with the operation's scope made explicit. No sibling tool performs token refresh, so an agent can distinguish it from update_account, get_account, and disconnect_account without inspection.

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?

Usage is implied by the operation (refresh tokens when they are stale or before an expiring call), but the description offers no explicit when-to-use, prerequisites, or sequencing relative to get_account/update_account. 'Safe to repeat' hints at re-invocation tolerance but does not define a trigger condition.

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