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

Annotations already declare the safety profile (readOnlyHint=true, openWorldHint=false, destructiveHint=false), yet the description still adds real behavioral detail: results are paginated and ordered newest first, non-group tokens are refused outright, and the group itself has no file and borrows its preview from its first displayable child. Auth/permission requirements are not mentioned, which keeps it short of a 5.

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?

Purpose and the sibling distinction are front-loaded in the first two sentences, which is the right ordering. It runs longer than strictly necessary — the palette/preview aside is contextual colour rather than call-critical information — but no sentence is filler.

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, no-output-schema list tool with fully documented parameters, the description covers the concept of a group, the routing decision, pagination ordering, and the error case. Only auth/permission scope and any rate-limit behavior are left unstated.

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 schema already documents page, per_page, fields, and organization, establishing a baseline of 3. The description goes beyond that by defining what a valid `token` is (`is_group` true in get_asset/get_assets) and what happens otherwise — meaning the schema does not carry.

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 opens with a specific verb+resource ('List the assets inside a group') and immediately differentiates itself from siblings by noting that list_assets and the search tools return only top-level rows. An agent can route to this tool without opening any schema.

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 explicitly states the alternative tools (list_assets, search tools) and the condition that selects this one over them. It also names a hard precondition for the required argument — `token` must be a group asset — so misuse is prevented rather than merely discouraged.

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