list_collection_folders

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful domain behavior beyond that: results carry item counts, and folder IDs 0/1 are reserved sentinels ("All", "Uncategorized") that an agent must recognize when passing IDs to other tools. It says nothing about ordering, auth, or whether the list is per-user.

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 short, front-loaded fragments with zero filler; the reserved folder-ID mapping is placed immediately. It is arguably over-terse rather than bloated, so the structure works even though the content is thin.

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 no output schema and 0% parameter coverage, the description carries the return-value burden and only partially meets it: it conveys that folders come with item counts and explains the two sentinel IDs, but not the shape of the result, ordering, or the role of username.

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 single parameter (username) has 0% schema description coverage, and the description never explains what it does or what happens when it is omitted (default null). Schema coverage is below the 50% threshold, so the description was required to compensate and does not.

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 names a specific resource (collection folders) and a distinguishing output trait (item counts), which lets an agent separate it from get_collection or collection_summary. It omits an explicit verb like "list", relying on the tool name to supply it, and does not contrast itself with siblings such as get_collection_fields.

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?

There is no statement of when to call this versus the other collection-listing siblings (get_collection, query_collection, collection_summary). The folder-ID hints imply this is the entry point for folder navigation, but that inference is left entirely to the agent.

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