subtitle.export_srt

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

There are no annotations, so the description must disclose behavioral traits. It only states the core function and does not mention side effects, default behaviors, or requirements. For example, it does not clarify what happens if the output file already exists or how config_path affects behavior.

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, focused sentence that immediately conveys the tool's purpose. It is appropriately sized and front-loaded, with no unnecessary words.

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?

Despite having an output schema, the tool has 4 parameters and no annotations. The description is too sparse to provide complete context, lacking details about default output locations, overwrite behavior, or how config_path modifies the export. This is a minimal viable description at best.

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 for explaining parameters. It only hints at transcript_path via 'transcript JSON file' but provides no meaning for overwrite, config_path, or output_path, leaving the agent with minimal guidance on required vs optional parameters.

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 exports a normalized transcript JSON file as SRT, specifying the verb, input resource, and output format. It implicitly differentiates from the sibling tool subtitle.export_ass by naming the output format, but it does not explicitly name that alternative.

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 provides no guidance on when to use this tool versus alternatives like subtitle.export_ass. It does not mention prerequisites, such as the need for a normalized transcript, nor does it explain the role of parameters like overwrite or config_path.

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