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

Annotations already cover safety (readOnlyHint, idempotentHint, non-destructive, openWorldHint), so the bar is lower, but the description still adds real value by disclosing the cached-vs-live distinction: 'refresh true asks Zernio for the live state' implies the default path may return stale data. It also flags that degraded connections appear in the result ('including any that need to be reconnected').

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 sentences, both front-loaded with the resource list first and the refresh behavior second. No filler or redundant restatement of the title. The second sentence is a compressed fragment, but it is efficient rather than confusing.

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 read-only, single-parameter tool with no output schema, the description covers what is queried, which providers are in scope, and what the refresh flag changes. The main residual gap is the shape of the returned status per provider (e.g., connected/expired/error), which the description only gestures at with 'need to be reconnected'.

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%, so the description carries the burden for the single parameter, and it does so: 'refresh true asks Zernio for the live state' explains the semantic difference between the true and default (false) values. It does not explicitly state that the default is a cached/local read, but that is strongly implied.

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 names a specific verb ('Status of') and resource ('account-level connections') and enumerates the concrete providers involved: Facebook, Google Drive, TikTok, and Zernio-mediated social accounts. That level of specificity separates it from vague siblings like get_connection_access or list_connections, though it does not explicitly distinguish itself from those siblings by name.

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 rather than stated: an agent can infer it should call this to check which integrations are healthy or need reconnecting. There is no explicit when-to-use vs. when-not-to-use guidance, and the closely related siblings (list_connections, get_connection_access, list_connection_catalog) are never mentioned or contrasted.

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