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

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world, so the safety profile is covered. The description adds the useful behavioral note that folders and assets come back in a single response and distinguishes browse vs search modes, but omits pagination behavior (default size/offset) and rate or volume characteristics.

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 tight sentences, no filler. The core action is front-loaded and the parameter guidance follows immediately.

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?

An output schema exists so return values need not be explained, and all 17 parameters are schema-documented. The description covers the browse/search split adequately. It falls short only on sibling disambiguation and pagination context, which are minor given the rich schema.

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 the schema already documents all 17 parameters including enums and defaults. The description calls out parent_id, title, status, and playlist_id as notable, adding mild emphasis but no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 with scope: 'List folders and assets for a workspace in a single response.' An agent knows this returns both folders and assets together, which implicitly separates it from list_folders. However, it never names siblings like list_folders, get_folder, or global_search to make the distinction explicit.

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 explains how to use two modes ('Use parent_id to browse a specific folder, or filters... to search assets'), which implies the browse-vs-search intent. But it gives no guidance on when to choose this tool over global_search, get_playlist_assets, or list_folders, and states no exclusions.

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