List CraftStory video models

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

No annotations are provided, so the description carries the burden. It discloses the returnable fields (status, modes, limits, credit prices) and, importantly, that a model can be in a 'paused' state, which is operational context an agent needs before invoking a generation sibling. It never explicitly states this is a read-only/no-input operation, so it stops short of full disclosure.

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 the purpose, then the routing advice. The parenthetical model summaries are somewhat long, but each clause carries decision-relevant detail (length ranges, audio vs description driven) that helps pick the right sibling tool.

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?

There is no output schema, but the description enumerates the returned content (status, modes, limits, credit prices) plus per-model capability summaries, so an agent knows what it will receive and how to act on it. Nothing needed to call a zero-param listing tool is missing.

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 tool takes zero parameters, which is the baseline-4 case. The description reasonably implies a no-argument listing call and adds no misleading parameter claims.

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 resource (catalogue of video models behind this server) and enumerates exactly what each entry contains: status, modes, limits, credit prices. The two named models (craftstory-2, minimax-h3) let an agent distinguish this from sibling creation tools like create_craftstory2_video.

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?

Explicitly routes the agent: 'Call this first when unsure which model fits, or to check that a model is not paused.' That is both a when-to-use and a stated alternative-selection rationale, with no inference required.

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