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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description goes further by disclosing default ordering (newest first), pagination behavior via pageNum, the returned field set (url, cover, size, workId) and the underlying endpoint GET /assets. No rate limits or auth caveats are given, but this is solid added context.

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?

Front-loaded with scope and content types, then the sibling disambiguation, then the endpoint. Efficient with no filler, though the single dense clause listing return fields compresses several facts into one sentence.

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, the description is the only source for return values, and it names the key fields plus ordering and paging. It omits total counts/cursor semantics, but for a five-parameter read-only list tool this covers what an agent needs to call it correctly.

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% with enums documented for sort and contentType, so the baseline is 3. The description only echoes the default sort and pageNum paging without adding format or constraint detail the schema lacks.

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 (list) and resource (an account's finished results: videos, images, audio) with scope ('finished results only') and names the sibling it is not (kling_list_tasks). An agent can distinguish it from kling_list_tasks, kling_list_running and kling_list_uploads 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?

Points to the alternative for the complementary case ('kling_list_tasks also shows running and failed tasks'), which effectively routes the agent to the right tool for running/failed work. It does not state prerequisites such as when the email parameter becomes mandatory, so it falls short of fully explicit when/when-not guidance.

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