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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine context beyond that: the semantic role of the assets (per-caption enrichment in the editor) and the fact that creation requires a presigned upload outside chat, which preempts a mistaken attempt to mutate the collection.

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?

Two tight sentences with no filler, and the core identity of the tool is front-loaded before the caveat about uploading. Every clause carries 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?

For a zero-argument, fully-annotated read-only listing tool with no output schema, the description supplies what an agent needs: what is listed, what it is for, and the one adjacent action that is unavailable. It stops short of noting return shape or pagination, which is acceptable given the absence of an output schema.

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?

The tool takes zero parameters, so there are no parameter semantics to document and the baseline is 4. The description correctly does not invent parameter detail.

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+resource ('List the account's uploaded B-roll clips') and scopes it to the account. The parenthetical explaining B-roll is used for per-caption enrichment disambiguates it from the many other list_* siblings (list_clips, list_clip_requests), though it never explicitly names the closest alternative.

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?

It tells the agent what is NOT possible ('uploading ... isn't available via chat'), which usefully prevents a dead-end call, but gives no positive guidance on when to reach for this versus clipember_list_clips or other listing tools. Usage is implied rather than stated.

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