image_resize

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It mentions input constraints (formats, 50 MB limit) and a no-enlargement behavior, but fails to explain output handling, such as whether original files are modified or new files are created. This is a significant gap for a resizing tool.

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 short and mostly efficient, with purpose front-loaded. However, 'Change the dimensions of a photo or picture' is redundant with 'Resize image,' adding a bit of filler. Still, the rest of the sentences provide meaningful constraints, so it earns a high score for conciseness.

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 tool has 7 parameters and no output schema, the description provides core purpose and key constraints (formats, size limit) but omits workflow specifics like output directory behavior (covered in schema) and multi-file handling. It is adequate but not fully comprehensive for a tool with this complexity.

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 input schema covers all parameters with descriptions, but the tool description adds valuable information not present in the schema, including accepted file types and the 50 MB size limit. It also clarifies the default 'fit' behavior with 'without enlarging.' This enriches understanding beyond the structured 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?

The description clearly states 'Resize image' with a specific verb and resource, and elaborates 'Change the dimensions of a photo or picture.' This distinguishes it from sibling tools like image_crop and image_rotate, which handle different operations.

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 a use case through 'Fits within your numbers without enlarging' and notes accepted formats and size limits, but it does not explicitly compare to alternatives or state when not to use this tool. It offers contextual guidance but no clear exclusions or alternative references.

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