KlingMCP

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

No annotations provided, so description carries full burden. It discloses the async nature by mentioning 'Task ID' in returns, implying a job-based pattern. However, it omits cost/credit implications, expected generation time, error handling (e.g., character detection failure), or data retention policies—critical details for a media generation API.

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?

Excellent structure with clear visual hierarchy: one-sentence purpose statement, explanatory elaboration, bulleted usage scenarios, and return type declaration. Information is front-loaded with the core function in the first sentence. No redundant or filler text; every section 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?

Given 7 parameters with 100% schema coverage and existence of output schema, the description adequately covers the tool's purpose, usage contexts, and return value (Task ID). However, completeness is limited by absence of annotations (costs, destructive hints) which the description does not compensate for, and lack of behavioral constraints or error condition documentation.

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 excellent field-level documentation (e.g., character_orientation enum values explained). The main description references 'reference video' and 'character image,' implicitly mapping to required parameters, but adds no syntax details, format constraints, or examples beyond what the schema already provides. Baseline 3 appropriate given comprehensive schema.

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?

Description opens with specific verb ('Transfer') and clear resource ('motion from a reference video to a character image'), immediately distinguishing it from sibling tools like kling_generate_video (which generates from text) and kling_extend_video (which extends existing videos). The second sentence reinforces with 'character animation' and 'extracting motion,' leaving no ambiguity about the core function.

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?

Contains explicit 'Use this when:' section with three concrete scenarios (animate character, create dance video, transfer specific movements), providing clear positive guidance. However, lacks explicit 'when not to use' guidance or named sibling alternatives, though the tool's specific scope makes incorrect selection unlikely.

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