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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the output is a hierarchical tree, but says nothing about read-only status, auth requirements (tenant_id auto-injection is only in the schema), pagination, or truncation behavior at max_depth.

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 tightly packed sentences with zero filler; the core purpose is front-loaded before the filtering note. Nothing could be cut 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 4-parameter list tool with full schema coverage but no output schema and no annotations, the description is minimally adequate. It conveys the tree return shape but does not describe response structure or how counts are returned, which the missing output schema leaves unexplained.

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 description coverage is 100%, so all four parameters (max_depth, tenant_id, parent_path, include_asset_counts) are already documented in the schema. The description names the path and depth filters but adds no syntax or format detail beyond what the schema provides, matching the baseline 3.

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 states a specific verb (List) and resource (collections) plus the return shape (hierarchical tree for organizing assets). It is clear what the tool does, though it offers no differentiation from the surrounding List*/Get* siblings.

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 only guidance is 'Supports filtering by parent path and depth,' which is really a parameter restatement. There is no when-to-use, no exclusions, and no routing against alternatives such as GetCollectionAssets or GetCollectionPublicUrls.

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