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

Adds substantial context beyond the annotations: the edit is saved as an undoable version (undo_edit), costs no Horizon Units, and is asynchronous, returning a job_id that must be polled via job_status then preview_frame. It also discloses a genuine limitation (rotation is only available in the RipClip editor). Slightly short of 5 because it doesn't say whether existing framing settings are replaced or merged when only some parameters are supplied.

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?

Efficiently front-loaded: trigger examples first, then parameter reference, then exclusions, then cost/return flow. Dense and mostly waste-free, though the parameter block reads as a single run-on sentence and could be broken up for faster scanning.

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 an 11-parameter mutation tool with an output schema, the description covers everything an agent needs: triggers, exclusions, every parameter's meaning and units, unit cost, undo semantics, and the post-call job_status/preview_frame sequence. Return-value details are correctly left to the 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?

Schema description coverage is 0%, so the description carries the full load and does so: clip_id provenance (list_clips, kind=photo for photos), zoom range 1-4 with the 1 meaning no zoom, position_x/y 0-100 with anchor semantics (0 = left/top, 50 = center), fit modes including the band shapes, background as blur or color name or hex, blur_amount 1-120, and custom_width/height bounds 240-4096 px. Only minor gap is that null/default behaviour for unspecified parameters is unstated.

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?

Opens with a specific verb+resource ('frame the picture in a clip or photo') and immediately disambiguates from siblings by naming style_clip (standard shapes), adjust_look (light/color), and edit_clip (facecam split) as out of scope. An agent can route to this tool on name alone without opening the schema.

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?

Gives concrete user phrasings that should trigger the tool ('zoom in a bit', 'show more of the left', 'make it 1200 by 628') plus an explicit 'Not for:' list mapping each excluded intent to the correct alternative tool. When-to-use, when-not-to-use, and alternatives are all stated.

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