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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return shape (id, name, slug, row and field counts, public flag) in the absence of an output schema, though it says nothing about pagination or ordering.

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?

A single front-loaded sentence with zero filler; the verb and scope lead and the returned fields follow. Nothing could be trimmed without losing information.

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 simple read-only list tool with one optional param and annotations covering safety, the description supplies the one thing structured data does not: the returned field set. Complete enough to invoke correctly, with only minor gaps (ordering, pagination, zero-collection behavior).

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?

There is one optional parameter ('id': 'Site id.') with 100% schema description coverage, so the schema already carries the meaning. The description confirms the listing is site-scoped but adds no format, default, or multi-site behavior detail beyond the 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 (List) and resource (the site's collections) and even enumerates what the listing contains (id, name, slug, row/field counts, public flag). It is easy to distinguish from singular get_collection or row-level list_collection_rows, though the description never names those siblings 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?

Usage is only implied: 'the site's collections' suggests a whole-site enumeration rather than a single-collection fetch or a row listing. There is no explicit when-to-use statement, no mention of get_collection/list_collection_rows as alternatives, and no note that it is an overview call.

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