crop_canvas

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

No annotations provided, so description must carry full behavioral load. It mentions discarding content but does not specify that it modifies the file in-place, whether it affects all frames, or if it is irreversible. Lacks details on mutation 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?

Description is a succinct docstring with a clear action sentence followed by parameter list. No unnecessary words, front-loaded.

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?

No output schema or annotations; description explains parameters and basic effect but omits return value, error conditions, whether it affects all frames or only current, and the scope of the destructive operation. Adequate but leaves gaps for a file-modifying tool.

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?

With 0% schema coverage, description fully explains all 5 parameters (filename, x, y, width, height) with clear docstrings. Provides meaning beyond schema.

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?

Description states 'Crop the canvas to the given rectangle, discarding content outside it.' Clearly specifies verb (crop), resource (canvas), and effect (discard). Distinguishes from sibling resize_canvas.

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?

Description implies usage via tool name and brief action, but does not explicitly state when to use vs resize_canvas or other alternatives. No prerequisites or exclusions mentioned.

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