motion_control

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

No annotations provided, so description carries full burden. It states 'Create a Kling task' and returns outputs, but fails to disclose whether the operation is synchronous or asynchronous, side effects, or required permissions. The presence of a 'wait' parameter in schema is not mentioned, which is a key behavioral detail.

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?

Description is very concise (one sentence) but lacks structure. It does not break down return values or provide examples. It is not verbose, but could be more informative without becoming long.

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 11 parameters, 2 required, no output schema, and no annotations, the description is severely incomplete. It does not explain the process, prerequisites, or the structure of the response beyond 'task id, status, and output URLs'. A more complete description is needed for effective use.

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 only 18% (only 'model' has a description). The tool description adds no meaning to any of the 11 parameters, despite required fields like source_image_url and reference_video_url lacking explanation. With low coverage, description should compensate but does not.

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 uses specific verb 'Create' and resource 'Kling task on RunAPI (motion control)', clearly distinguishing it from sibling tools like image_to_video or text_to_video. It also mentions return values, providing a clear purpose.

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?

No guidance on when to use this tool versus alternatives. The description does not list prerequisites or scenarios where this tool is preferable over siblings, leaving the agent to infer usage.

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