studio_caption

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

With no annotations, description fully covers behavior: show/replace functionality, fade-out via clear=true, placement (bottom-left), and timing constraints. No contradictions.

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?

Three concise sentences; first sentence defines purpose, second gives style and timing guidelines, third explains the clear parameter. No redundancy.

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 simple tool with 3 optional parameters, the description covers all necessary context: placement, style, constraints, companion tool (studio_hold), and fade-out usage. Complete for AI agent invocation.

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 100% (baseline 3). Description adds value by providing word count and timing constraints for caption_text, and context on eyebrow as a kicker. But does not add meaning beyond schema for clear parameter.

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?

Description clearly states the tool shows or replaces a bottom-left storyline caption with an eyebrow kicker and sentence, narrating the current beat. It is distinct from sibling tools like studio_hold (timing) and studio_highlight (visual emphasis).

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?

Provides specific usage guidance: keep captions under ~12 words, use studio_hold for 2-4s display, and pass clear=true for scene changes. However, does not explicitly state when not to use or mention alternative tools.

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