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

Annotations declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, but the description only says "refresh," which reads as a benign status re-check and gives no hint that state may be invalidated or that the call is not safely repeatable. It also omits what happens to an existing verified voice_id and whether support intervention is a side effect of calling or only a fallback.

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 with no filler, and the core action is front-loaded. Slight deduction because the second sentence spends words on a downstream support workflow rather than on the call itself.

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?

An output schema exists, so return values need not be explained, but the description leaves key gaps for a non-idempotent, destructive, open-world mutation: no statement of retry behavior, no note on what state changes on the voice, and no clarification of the single undocumented parameter.

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 single parameter voice_id has 0% schema description coverage and is never mentioned in the description, so nothing clarifies whether it is the provider-side voice identifier or the local voice record. The name is largely self-explanatory, keeping this at baseline rather than lower.

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?

"Refresh provider verification status" names a verb and a resource, and it is clearly distinct from siblings like create_voice, delete_voice, and get_voice_preview. However, "refresh" is ambiguous — it does not say whether this re-triggers a check, polls the provider, or mutates the voice's verification state, and "provider" is never defined.

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?

The description gives no condition for when to call this versus list_voices or get_voice_preview, and no prerequisites. The second sentence describes what happens after the call (user must finish verification with support), which is outcome information, not guidance on when to invoke it.

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