crop_image

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

With no annotations, the description must carry the behavioral disclosure burden. It discloses key behaviors: it saves the cropped image and returns the path and new dimensions, and supports edge expansion. However, it does not describe the return format or what happens if out_path is omitted, and it leaves coordinate system defaults to the schema.

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 a single, front-loaded sentence that states the core action first ('按坐标裁切图片') and adds supplementary details. Every word adds value, with no redundancy or filler.

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?

The tool has 5 parameters, no output schema, and no annotations. The description adequately conveys the main operation and result, but it lacks details on return value structure and parameter semantics for image/out_path. Given the complexity, it is minimally viable but not fully complete.

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 60%, and the description adds some meaning beyond the schema by explaining the purpose of coordinates and edge expansion, and mentioning output path. It does not clarify the 'image' parameter or 'out_path' parameter in detail, but it partially compensates for the coverage gap.

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 crops an image by coordinates, with optional edge expansion, and saves/returns the result. This is a specific verb+resource combination that is distinct from sibling tools like ocr_image or describe_image, which have different purposes.

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?

The description implies usage (crop an image when needed) but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions. It does not mention scenarios like 'use this instead of zoom_region' or when not to use it.

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