Create Series

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

With no annotations, the description carries the behavioral burden and discloses real context: files are pushed straight to the creator's Bunny Stream library (an external destination), a hard cap of 100 episodes, ordering semantics, and the readiness condition for accepting orders. It omits permissions, failure behavior, and whether re-invocation is idempotent, but the mutation's side effects are unusually well surfaced.

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?

Four sentences, front-loaded with the commercial purpose before constraints and ordering rules. Parentheticals are dense but each carries information (what a series is, natural sort order), with no filler.

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 10-parameter creation tool with no annotations and no output schema, the description covers destination, ordering, limits, and readiness well, but says nothing about the return value (siblings like get_upload_job imply an async upload job) or auth/permission requirements. Adequate but leaves a notable gap for the caller.

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 coverage is already 90%, so the baseline is 3; the description earns above that by adding meaning the schema lacks, notably the 100-episode limit (the schema's episodes array only sets minItems) and the coupling of freeCount to the readiness rule ('at least freeCount + 1 episodes'). The folder natural-name-ordering note reinforces the episodes parameter's dual string/array form.

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 verb and resource: sell a series of episodes (short drama / web series) for one price with the first few free. The parenthetical defines the domain concept and implicitly distinguishes it from create_video and create_gallery, though it never names those siblings. An agent can tell what this tool creates without opening the 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?

Usage is implied by the domain description (multi-episode monetized series) and a readiness precondition is given: 'takes orders once at least freeCount + 1 episodes (and at least 2) are ready.' There is no explicit when-to-use-vs-alternative routing, so the agent must infer that add_episodes / create_video are the other paths.

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