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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds genuinely useful behavior the annotations don't: the id prefix convention (u_ = yours, o_ = official), the fact that a quota consumption figure is returned, and that cover/tags accompany each element. It stops short of describing pagination behavior or total counts.

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?

A single dense, front-loaded sentence that packs the tool's identity, output fields, and quota note without filler. The nested parentheticals and id examples make it slightly run-on, but nothing is redundant and 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?

With no output schema, the description carries the burden of describing the return payload - and it does, listing id, name, type, cover, tags and quota usage. That covers most of what a 7-param list tool with optional filters needs, though pagination semantics and whether official and own elements can be mixed in one call remain unaddressed.

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 every one of the 7 parameters is already documented in the schema, establishing a baseline of 3. The description only lightly echoes the 'official' flag and tag source, adding no syntax or format detail beyond what the schema already states.

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+resource ('List elements' / GET /elements) and enumerates what an element is: reusable characters, props and scenes. It distinguishes itself from siblings kling_get_element (single fetch), kling_list_element_tags, and kling_create_element by naming the consuming tools and showing the element id/type/cover shape.

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?

Usage is implied (browse your or official elements) and the tag parameter routes the agent to kling_list_element_tags first, which is a helpful dependency hint. But there is no explicit when-to-use guidance versus kling_get_element or kling_list_element_voices, and no statement of when to prefer official=true over your own elements.

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