generate_speech

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

Since no annotations are provided, the description carries the full burden. It discloses the requirement for Resolve Studio and a specific package, and describes creation and timeline placement. However, it does not cover failure scenarios, error conditions, or what happens if prerequisites are missing. This is adequate but not comprehensive.

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 well-structured with an overview followed by parameter details. It is clear and front-loaded, but the Args section could be slightly more compact. Overall, it earns its length without being verbose.

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?

Given 11 parameters, no annotations, and presence of an output schema, the description covers the function, prerequisites, and parameter roles adequately. It does not need to explain return values since an output schema exists. The description is sufficient for an agent to understand and invoke the tool correctly.

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 0%, so the description must compensate. It provides an Args section that explains each parameter in detail, including timecode format, voice model examples, and relationship between custom_voice_file and voice_model. This adds significant meaning beyond the schema's minimal titles and defaults.

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 it generates speech audio from text using DaVinci Resolve's AI Speech Generator, creating a MediaPoolItem and optionally adding to timeline. This distinguishes it from sibling tools like import_audio (import existing files) and transcribe_audio (opposite direction).

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 includes prerequisites (Resolve Studio with AI Speech Generator package) and indicates when to use (text-to-speech generation). It does not explicitly state when not to use or compare to alternatives like import_audio, but the context is clear enough for an agent to decide.

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