screenslick_generate_transcript

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

No annotations are provided, so the description must disclose behaviors. It does not mention side effects (e.g., whether it modifies the timeline, adds tracks, or requires an existing video), nor any authentication or rate limits. The verb 'run' implies action but lacks detail.

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 sentence, which is concise but lacks necessary detail. It is front-loaded with the core action, but brevity comes at the expense of completeness for a tool with 4 parameters.

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 4 parameters, no required fields, and no output schema, the description is insufficient. It does not explain the return value, prerequisites, or how the input parameters affect the result, making it hard for an agent to use 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 coverage is 0%, meaning no descriptions exist for any of the 4 parameters. The tool description adds no information about language, modelSize, provider, or enableSubtitles, leaving the agent without guidance on what these parameters control or how to set them.

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 runs a transcription/subtitle generation flow on the current video or timeline. It distinguishes from siblings like generate_script or generate_voiceover, though it could be more precise about what exactly is produced (e.g., transcript text vs. subtitle tracks).

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?

No guidance on when to use this tool versus alternatives like generate_script or add_transcript_voiceover. The description only states what it does, not the context or prerequisites for usage.

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