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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, so the safety profile is largely covered. The description adds useful context (no cost, may update saved connection status), but 'may update' is vague and does not explain what a destructive refresh actually invalidates or changes.

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, front-loaded sentences with the action first and the cost/side-effect qualifier second. Nothing is padded or repeated.

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?

Annotations cover the safety profile and there is no output schema to explain, so the description only needs to convey action and side effects. It does that for a one-parameter tool, though it omits what happens when verification fails or whether the refresh is rate-limited.

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 coverage is 0% and the single property carries no description, so the description is the only source of meaning. 'One connected hostname' usefully narrows the parameter to an existing connected host rather than an arbitrary string, but adds no format, validation, or identification guidance.

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 (DNS verification) scoped to 'one connected hostname', which is distinct from domain_connect, domain_disconnect, domain_list, and domain_search. It does not explicitly name the sibling tools it must not be confused with, but the purpose is unambiguous.

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 phrase 'one connected hostname' implies the precondition that the hostname is already connected, and 'Free' tells the agent cost is not a gating factor. However, there is no explicit when-to-use/when-not guidance or routing to alternatives like domain_connect for a hostname that is not yet connected.

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