bdesign_asset_extract_frame

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

Annotations already state destructiveHint false; the description adds that it returns a PNG frame and gives position guidance, but does not disclose additional side effects or error behavior.

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?

Single sentence, direct and free of unnecessary detail.

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?

Provides enough context to know it extracts frames from video assets, but lacks mention of return format details and edge cases; however, the schema covers required parameters.

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 0%; only the position parameter receives a hint about using 'last' for tail-frame continuation. assetId and projectId are not explained.

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 clearly states the tool extracts a PNG frame from a project video asset, with a specific verb and resource, and distinguishes it from other asset and editor tools.

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 provides a hint to use position 'last' for tail-frame continuation, but does not explicitly compare with alternative tools like bdesign_asset_get or bdesign_canvas_continue_from_tail.

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