Crop, scale, rotate

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

The description discloses operation ordering (crop, scale, pad, rotate, flip) and the cost implication of a single re-encode. This adds value beyond the sparse annotations, which only show readOnly/ destructive hints without explaining the transform 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?

The description is compact and well-structured, front-loading the main purpose and then providing the most critical usage nuances. Every sentence earns its place without unnecessary fluff.

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?

Given the complexity of 10 parameters and the presence of an output schema, the description sufficiently covers the key behavioral aspects: operation order, encoding cost, and aspect ratio handling. It could be more explicit about alternative tools, but it is adequate for correct invocation.

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 description adds essential interplay semantics: giving only one scale dimension preserves aspect ratio, while giving both with pad_to_fit letterboxes instead of stretching. This compensates for the moderate schema coverage (50%) by clarifying how the scaling and padding parameters relate.

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 applies geometric transforms (crop, scale, rotate, flip) in a single pass. It differentiates from siblings by emphasizing the one-pass composable chain, which is distinct from simpler tools like resize_video or track_and_crop.

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 specific guidance on using scale_width/scale_height and pad_to_fit to control aspect ratio behavior, which helps agents use parameters correctly. However, it does not explicitly name alternative tools or state when to prefer this tool over sibling operations.

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