kling_list_actions

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns a 'categorized list of all actions and their corresponding tools,' which is sufficient for a read-only listing operation with no side effects. No contradictory behavior is mentioned.

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?

Three concise sentences, front-loading the primary purpose. Every sentence adds value: listing action, reference guide, return description.

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 simple 'list all' tool with no parameters and an output schema, the description fully explains what it does and returns. It covers the necessary information for an agent to use 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?

The input schema has zero parameters with 100% coverage (since none exist). The description adds value by specifying the return is a categorized list, which goes beyond the 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 states 'List all available Kling API actions and corresponding tools,' clearly specifying the verb (list) and resource (actions and tools). This distinguishes the tool from its siblings, which are concrete action tools like kling_generate_video or kling_list_models.

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 description positions the tool as a 'reference guide for understanding the full capabilities,' making its use case clear. However, it does not explicitly state when not to use it or mention alternatives, though the sibling tools list implies differentiation.

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