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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the connection-to-site cardinality model and what state is surfaced (autopilot on/off, weekly volume, paused), which is context beyond the structured fields, but says nothing about errors or edge cases when no site is connected.

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 tight sentences, front-loaded with the scope-defining clause before the detail list. Slight redundancy in re-enumerating return fields that an output schema already documents, but it reads as a useful scan-level summary rather than padding.

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 zero parameters, an output schema covering return values, and annotations covering the safety profile, the description only needs to add scope semantics — and it does, explaining the one-site-per-connection model that no structured field captures. Nothing needed to call this tool correctly is missing.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly adds no parameter discussion, keeping the description focused on scope rather than inputs.

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 (list) and resource (the site this connection reaches) and enumerates what comes back: id/workspace id, name, tracked domains, autopilot state, cadence, and paused flag. It is clearly distinguishable from list_domains/list_articles by being singular and connection-scoped, though it never names a sibling tool explicitly.

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 second sentence supplies real usage context: a connection reaches exactly one site, so this tool is not for enumerating multiple sites, and getting another requires reconnecting or adding a CLI profile. That is an implicit exclusion plus a workaround, but there is no explicit routing to an alternative tool for multi-site cases.

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