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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds real behavior beyond that: collections hold references rather than copied content, start private, private/withdrawn collections return 404, and responses are private/no-store. Some of the publication semantics apply to public reads rather than this list tool, but the added context is substantive.

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?

The opening sentence is front-loaded and useful, but the remaining clauses drift into publication and caching semantics that are tangential to listing one's own collections. Several sentences do not clearly earn their place for this specific tool.

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 read-only list tool with no output schema, the description communicates state and privacy constraints but says nothing about the returned collection shape or pagination behavior (other than the schema's cursor param). Adequate but with clear gaps for how results are delivered.

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?

Only one parameter ('after') and schema description coverage is 100%, so the schema fully documents the cursor semantics ('document cursor from the next-page URL. Do not construct it.'). The description adds nothing about the parameter, so 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?

States a specific verb and resource ('List collections') and scopes it to the personal account, which implicitly separates it from the sibling team_list_collections. It does not name that sibling explicitly, but the scope qualifier lets an agent distinguish the two.

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 'personal account' qualifier implies when this tool is appropriate versus team-scoped variants, but there is no explicit when-to-use/when-not guidance or named alternative. Usage context is inferable rather than spelled out.

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