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

Goes well beyond the annotations by disclosing that encoding is asynchronous and returns immediately, that the response lists both queued and skipped files with skip reasons (not found, not a video, already queued/encoding), and critically that already-encoded files will be re-encoded if sent again. That last point corroborates the non-idempotent, destructive annotation with concrete operational 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 purpose is front-loaded in the first clause and nearly every sentence carries operational value. The final clause about checking status after a timeout partially repeats the earlier polling guidance, and the middle sentence is dense with parenthetical skip reasons, so it is not maximally tight.

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 still explains what the call returns (queued and skipped files with reasons) and how to determine completion. For a single-parameter async queue operation, nothing an agent needs to invoke it correctly is missing.

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?

There is a single parameter (fileIds) with 100% schema description coverage, including the pattern, min/max items, and the source listing tool, so the schema carries the burden. The description does not add syntax or format detail beyond what the schema states, so the baseline of 3 applies.

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 ('Queue video files for encoding so they can be streamed') and explains the reason encoding is needed, which cleanly separates it from siblings like livereacting_get_media_file and livereacting_get_encode_status that it explicitly names.

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?

Gives explicit when-to-use criteria (resolution or frame rate above the account limit), tells the agent how to identify candidates (livereacting_get_media_file with includeMetadata), and names the follow-up tool to poll. It also adds a caution: do not re-send already-encoded files, and check livereacting_get_encode_status after a timeout before retrying.

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