process_design_image

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

The description discloses important behavioral traits: operations are 'ordered deterministic' and background removal is 'classical, not AI matting'. This adds context beyond the schema, especially since no annotations are provided, though it does not cover failure modes or permissions.

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 only two sentences, highly concise, and front-loaded with the core capability before detailing the operation types. Every word contributes 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?

Given the rich input schema that fully explains all parameters, the description gives a solid high-level overview. However, with no output schema, it does not mention the return value or confirmation of file output, leaving a minor gap for agents expecting a response.

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 descriptions cover 100% of parameters with meaningful details (paths, filename constraints, operation arrays). The description's listing of operation types adds no new semantic meaning beyond what the schema already provides, so it remains at baseline.

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 uses a specific verb 'Apply' and enumerates the exact operations (crop, scale, pad, remove-flat-background, trim-transparent), making the tool's function unambiguous. It clearly distinguishes from sibling design/layout tools which are unrelated to image processing.

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 the tool is used for image operations that require ordering, but it does not explicitly state when to use it versus alternatives or when not to use it. No exclusions or alternative tool references are given, so usage guidance relies on inference.

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