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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that the filters act as optional steering alongside the seed ids, which is useful. It does not mention credit cost of the base call, default limit, or that clips raises cost, though the schema covers the clip cost.

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 compact sentences, front-loaded with the core action and then the refine-loop rationale. No filler; only mild loss from the quoted example phrase eating space that could note the return shape.

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 21-param similarity search with no output schema, the description conveys the seed-plus-steering model an agent needs to call it plausibly. Still missing the interaction between shot_ids and the 20 optional filters, and any hint of result shape or default limit.

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 coverage is 57%, so the schema handles roughly half the 21 parameters. The description adds the key semantic point that the tag/filter params steer similarity rather than hard-restrict, which is beyond what the schema says. It leaves ambiguous whether filters combine with shot_ids or override them.

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: returns shots similar to given shot_ids. The 'refine loop: more like #2' framing makes the operation concrete. It does not name the nearest sibling (find_similar, search_commercial_shots) to disambiguate, so it falls 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?

'from earlier results or a shot list' implies the tool depends on a prior search, and 'refine loop' hints at iterative use. But there is no explicit when-not-to-use guidance or comparison to find_similar / search_commercial_shots, which sit right next to it in the list.

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