Split Chapter to Scenes

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

No annotations are provided, so the description carries the full burden of disclosure. It does reveal the auto-assignment of checklist and filtering by chapter.kind, but does not disclose destructive effects, permission needs, or what happens to the original chapter or existing scenes.

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?

The description is a single short sentence that conveys both the core action and a key behavioral detail. It is front-loaded and free of unnecessary wording.

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?

Without output schema or annotations, the description is under-specified for a mutation tool. It omits return value, side effects, edge cases (e.g., existing scenes), and prerequisites, providing only the basic split-and-assign behavior.

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 33% (only n has a description). The description mentions 'N' and chapter.kind but does not clarify project_id or chapter_id semantics beyond their names, nor does it explain parameter interactions or constraints 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?

The description clearly states the tool splits a chapter into N scenes and auto-assigns checklist filtered by chapter.kind. It uses a specific verb and resource, and this distinguishes it from other chapter/scene tools like update_chapter or update_scene.

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 implies usage (when you need to split a chapter into scenes) but does not explicitly mention when to use vs alternatives or any exclusions. Prerequisites and conditions for use are not clarified.

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