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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safe read-only nature is covered. The description adds the thumbnail detail, but doesn't mention pagination behavior for the limit parameter or ordering of results.

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 sentences, no filler, with the catalogue scope front-loaded and the usage note trailing. Every clause earns its place.

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 zero-required-param read-only list tool with no output schema, the description covers purpose and filters but leaves the limit parameter undocumented and gives no sense of result ordering or pagination despite the 100-item cap in the 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 coverage is 0%, so the description must compensate. It names the four filter dimensions (query/gender/nationality/tag) but omits the limit parameter entirely and provides no format or value hints (e.g., accepted gender/nationality values) for any filter.

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 (curated SeedDance digital actor catalogue), and adds the useful scope note '(with thumbnails)'. It distinguishes itself from list_seedance_library by naming the actor catalogue specifically, though it doesn't explicitly contrast with that close sibling.

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 final sentence 'Use an actor when composing a SeedDance generation' provides clear downstream context for why an agent would retrieve this list. However, it does not mention when to prefer this over list_seedance_library or other catalogue tools.

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