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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, lowering the bar, but the description adds only the vague claim 'client and server side' and a vendor string. It does not say that the source video is left unmodified, that the result is returned as a new (base64) video, or anything about size limits or processing latency — relevant for a media-burn operation.

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 action is front-loaded in one sentence, which is efficient, but the sentence is a run-on padded with 'client and server side from freedailypro' — filler that dilutes rather than earns its place.

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 two required parameters and no output schema, the description should carry the remaining load: it does not explain the return value (presumably a processed video), the encoding of fileBase64, or any constraints. For a transformation tool it leaves an agent short of what it needs to invoke 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 50%: 'srt' is documented in the schema, but 'fileBase64' has no description anywhere. The description says subtitles are burned into 'a video' but never clarifies that fileBase64 is the encoded source video or what format/size is accepted, so it does not compensate for the coverage gap.

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?

States a specific verb and resource ('Burn SRT subtitles ... into a video') and names the input format (SRT), which separates it from siblings like generate_captions or video_convert. The trailing phrase 'client and server side from freedailypro' is noise that adds no discriminating power, but the core action is 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?

There is no when-to-use or when-not-to-use guidance. The description never mentions alternatives such as generate_captions (which produces a caption track rather than embedding it) or video_convert, so an agent must infer routing from the name alone.

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