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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that the response includes render counts and download links, which hints at a polling/retrieval use case, but does not state whether the batch must be complete or whether the data is eventually consistent. Modest added value above the annotations.

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?

A single front-loaded sentence that lists the four returned artifacts with no filler or repetition. Nothing could be trimmed without losing information.

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 the description need not document return values, and it is adequate for a two-parameter read tool with full annotations. The gap is routing: with siblings clips_status_get, clips_inspect, and clips_list in the same namespace, the description never helps the agent choose this one over those.

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 100% for both parameters, so the schema already explains batchId and the optional workspaceId default. The description adds no syntax, format, or scoping detail beyond what the schema provides, making the baseline of 3 appropriate.

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 names a specific verb ('Get') plus resource ('a BlitzReels clip batch') and enumerates what comes back: status, generated clips, render counts, and download links. That is more informative than a bare 'get batch'. It does not, however, distinguish this tool from the closely named sibling clips_status_get, leaving some ambiguity about which retrieval endpoint to pick.

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 guidance, no preconditions (e.g. batch must be finished rendering), and no mention of alternatives such as clips_status_get or clips_list. The agent must infer usage purely from the name and the description's field list.

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