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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds that results span heterogeneous connection kinds and include connectivity flags for a few named services, but says nothing about scope (all connections in the account), result size, or whether disconnected entries appear.

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, front-loaded with the core definition, followed by the boundary and a URL. The parenthetical enumeration is slightly wordy but earns its place by defining 'connection'; the URL is functional rather than filler.

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?

With no output schema, the description does its part by hinting at the return shape (a set of connections plus connected/not-connected indicators). But for a 1-parameter list tool it leaves the filtering behavior and result completeness unstated, so an agent cannot fully predict what it gets back.

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 100% and the provider parameter is already documented with examples (mcp, imap, google_drive, zoom). The description does not mention the provider filter at all, so it adds no meaning beyond the schema; baseline 3 applies.

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 states the resource precisely and even defines what counts as one connection ('each mailbox, Drive view, MCP server, app account'), which is genuinely clarifying for an ambiguous domain term. It reads as a noun phrase rather than an explicit verb, so listing is implied by the name rather than stated.

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?

It draws a useful boundary by telling the agent that connecting, disconnecting and sharing happen on the Connections screen, which steers it away from expecting mutation via this tool. However it never names the relevant siblings (get_connection_status, get_connection_access, list_connection_catalog, list_integrations) or when a per-connection lookup is preferred over this list.

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