video_subtitles_styled

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

With no annotations provided, the description carries the full burden of disclosing behavior. It notes the function embeds subtitles and returns a success dict, but omits important details like whether the operation is destructive (overwrites output), required permissions, codec constraints, or error handling.

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 extremely concise: two sentences plus a structured docstring with minimal words. Every sentence adds value, and the format is easy to scan.

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?

The presence of an output schema reduces the burden, and the description covers the return type. However, it lacks information about edge cases (e.g., invalid paths, unsupported subtitle formats) and dependencies (e.g., ffmpeg). For a tool with 4 parameters, this is adequate but not thorough.

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?

The schema has 0% description coverage, so the description compensates by listing each parameter with a brief explanation. For the 'style' param, it provides useful hints about allowed fields (font, size, color, outline), adding significant meaning beyond the raw schema.

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 burns subtitles from SRT/VTT files with custom styling, distinguishing it from sibling tools like video_subtitles (generic) and video_generate_subtitles (generation). The verb 'burn' and resource 'subtitles with custom styling' are specific and unambiguous.

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 does not provide any guidance on when to use this tool versus alternatives such as video_subtitles. There is no mention of prerequisites, use cases, or exclusions, leaving the agent without context for appropriate invocation.

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