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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive context beyond them: the permission encoding (1 read, 2 read-write), the meaning of rootParentId and its linkage to create_page for top-level pages, and the response-size tradeoff exposed by `exclude`.

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?

Four short sentences, front-loaded with the purpose, then prerequisites, then response shape, then the recommended agent action. No sentence is redundant given there is no output schema to carry the return-field details.

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 only two parameters, full schema coverage, and no output schema, the description compensates by describing exactly what comes back (id, name, type, permission, rootParentId) and by linking the tool into the surrounding workflow. Nothing needed to call it 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it tells the agent where orgId comes from (list_organizations) and explains why `exclude` exists (to keep the response small), rather than merely echoing the schema's example values.

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 uses a specific verb and resource ('List the collections (docs sites) in an organization') and enumerates the returned fields (id, name, type, permission, rootParentId), which clearly separates it from siblings like list_organizations and list_collection_pages.

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 supplies the prerequisite chain ('Get orgId from list_organizations'), an optimization hint ('Pass exclude=runCollection,environment to keep the response small'), and an explicit workflow instruction ('Ask the user which collection to work in'), so an agent knows exactly how and when to reach for this tool.

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