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

Annotations already declare destructive=true, idempotent=true and openWorld=true, so the bar is lower, yet the description adds a material cost disclosure ('Can spend existing credits') that annotations do not carry. It also notes screen-context preservation through the layout pipeline, a side effect an agent would not otherwise know about; it stops short of quantifying credit spend or describing the batch lifecycle.

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?

Three tight sentences, front-loaded with the action and source, then side effects, then the next step. The phrase 'through the existing layout pipeline' is slightly internal jargon but still 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 an output schema present the description need not explain return values, and it correctly points at batch_id for the follow-up call. For a destructive, credit-spending, open-world operation the description covers cost and safety adequately, though it omits any indication of credit magnitude or failure behavior.

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, and it only covers three of six parameters ('clip count, maximum duration and caption look'). It adds the useful nuance that these are optional, but workspaceId, recordingSetId and idempotencyKey semantics are left entirely to the 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?

States a concrete verb and output ('Produce a batch') plus the exact source resource ('a ready synchronized camera and screen recording'), which separates it from recording_sets_finalize and clips_create. It does not name a sibling explicitly, so it stops short of a 5.

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 a precondition ('ready synchronized recording') and a follow-up step ('follows clips_get with the returned batch_id'), which is real guidance. It never states when to prefer this over clips_create or other clipping entry points, and no exclusions are given.

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