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

With no annotations, the description carries the full burden and largely meets it: it discloses the exact return shape, that no limit/offset exists, and that the pagination block reports truncated=false with a count so a complete list is distinguishable from a first page. It does not explicitly state the read-only/no-side-effect nature, but the verb 'List' makes that clear.

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?

Three sentences that are front-loaded with the resource and its fields, then usage, then pagination semantics. Slightly dense but every clause carries information; no 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?

No output schema exists, so the description must explain return values, and it does so thoroughly (per-field contents, connections block, pagination block). Combined with the usage routing, an agent has everything needed to call and interpret the tool.

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?

Zero parameters, so baseline is 4. The description goes further by explaining there is intentionally no limit or offset to pass and why, which adds useful meaning beyond the empty schema.

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 and resource ('List every site on the account') and enumerates exactly what each entry contains (name, domain, public URL, default language, connections block with per-source connected flags and last-sync times). An agent can distinguish it from Site_Details or All_Sites_Overview without opening any schema.

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?

Explicitly tells the agent to 'Start here to find the site_id every other tool needs, and to check a source is connected before asking for its data.' That is an unambiguous when-to-use directive tied to downstream siblings.

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