generate_character_sheets

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

With no annotations, the description carries full behavioral burden. It reveals batching behavior, no duplicate billing, pay-per-use, 2–4 minute pending window, ready vs rejected states, how to read sheet_fail_hint, retry policy, and when to run precheck. Exceptionally transparent for a generation tool.

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 long but information-dense: purpose, prerequisite, billing, and status handling each earn their place, and the main action is front-loaded. Slightly dense single paragraph, but justified given no annotations.

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?

Covers preconditions, monitoring, failure modes and recovery in detail, which is crucial because there is no output schema and no annotations. The only material omission is documentation of the episode_id parameter and the immediate call result/return value; otherwise it is complete.

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 sole required parameter episode_id is never mentioned in the description, and schema coverage is 0%. With no description coverage, the tool should explain how episode_id relates to the 'whole-drama' scope; its absence leaves an agent to guess whether to use drama_id, episode_id, or project context. Schema type/required are the only clues.

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?

Clearly identifies batch generation of multi-view turnaround design sheets for all characters in the drama, and explicitly states it only generates for characters lacking sheets. This distinguishes it from sibling portrait/prop/sheet tools and states the resource and verb.

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?

Gives explicit prerequisite (character must have a definitive portrait), states it blocks and prompts if missing, instructs polling get_characters for sheet_status instead of re-clicking, and provides retry/conflict routing to run_precheck. This is explicit when-to-use and when-not-to-use guidance.

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