List CraftStory video models

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantive behavior by disclosing the return contents (status, modes, limits, credit prices) and the pause/pricing state that a follow-up call must respect. It does not cover auth requirements or whether the model roster can change, but for a zero-parameter read-only listing this is substantial added value.

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-loads the catalogue purpose, then the per-model breakdown, then the usage cue. Dense but each clause carries information an agent uses for model selection; the parenthetical model details are somewhat heavy but not redundant.

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, so the description must convey what a caller learns. It does so by naming the models and the dimensions returned (status, modes, limits, prices) and by telling the agent when the result matters (paused checks, model fit). Nothing needed to invoke a zero-param listing correctly 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 no parameters, so the baseline is 4. The description adds no parameter guidance, and none is needed; the schema is trivially complete.

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 (the catalogue of video models on this server) and enumerates exactly what it exposes: status, modes, limits and credit prices. It even names the two models with their capabilities and durations, so an agent can distinguish this discovery tool from execution siblings like create_craftstory2_video without opening any schema.

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 says to call this first when unsure which model fits, or to verify a model is not paused, which is clear actionable context. It stops short of naming the alternative execution tools to route to after resolving the choice, so the when/when-not framing is present but not fully closed.

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