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

Annotations already indicate a non-read-only, non-idempotent operation, and the description adds useful context: hosted URL output, return shape, optional caption cues, and key requirements. There is no contradiction between the description and the annotations.

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 front-loaded with the core purpose and return value, then gives downstream integration and prerequisites. It is compact, though the final sentence about fully-voiced reels is somewhat promotional and could be trimmed without losing critical information.

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?

With no output schema, the description correctly provides the return shape, optionality of cues, downstream consumption via neuron_studio_apply, and prerequisite keys. For a moderate 4-parameter tool with no nested inputs, this fully equips an agent to call it correctly and use the result.

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 100%, so the baseline applies; the description does not need to repeat parameter details. It adds a small amount of meaning around caption cues and the transcription key requirement, but not enough to push above baseline.

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 states a specific action—converting a script into a hosted voiceover audio URL—and notes optional synced caption cues. It is clearly distinct from image/video generation and transcription tools, though it does not explicitly name a sibling to differentiate against.

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 gives clear downstream context: the result should be placed with neuron_studio_apply via add_audio and add_captions, and it states the prerequisite keys for TTS and captions. It implies the use case of fully voiced reels, but it does not explicitly list alternatives or when-not-to-use cases, so it stops short of a 5.

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