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

Adds real behavior beyond the annotations: cost impact ('Can spend existing credits'), a processing guarantee ('Preserves readable screen context through the existing layout pipeline'), and the async workflow handoff via batch_id. Annotations already declare the mutation/idempotency profile, so this extra context earns credit.

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 compact sentences, front-loaded with the core action and free of filler. The cost and workflow notes are appended efficiently rather than padded.

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?

An output schema exists, so return values need not be described, and the description covers the batch_id handoff, cost, and processing behavior. The main gap is the undocumented idempotencyKey and workspace scoping, but overall it is sufficient to invoke the tool 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 description coverage is 0%, so the description must carry parameter meaning, and it only covers three of six params (clipCount, maxDurationSeconds, captionThemeId). It never mentions workspaceId, idempotencyKey, or recordingSetId, nor does it explain the allowed duration values or the credit-relevant limits that a caller would want.

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 ('Produce a batch from a ready synchronized camera and screen recording'), which distinguishes it from the generic clips_create sibling by tying it to recording sets. It is clear but does not explicitly name the alternative tools (clips_create, clips_candidates_list) an agent might confuse it with.

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?

Implies a precondition ('a ready synchronized recording') and gives a follow-up step ('follows clips_get with the returned batch_id'), which is useful sequencing guidance. However, it never explicitly says when to use this instead of clips_create or what state the recording set must be in, leaving the routing decision to inference.

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