resize_image

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: it uses 'AI outpainting to intelligently extend content' (implying content generation beyond simple scaling) and notes that some modes are 'coming soon' (managing expectations). However, it doesn't mention critical aspects like rate limits, authentication needs, file size limits, processing time, or what happens to image quality. For a tool with AI generation capabilities, this is a significant gap.

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 appropriately concise with three sentences that each serve a purpose: stating the core function, explaining the AI method, and noting upcoming features. It's front-loaded with the main purpose. The only minor inefficiency is the parenthetical '(like Canva Magic Resize)' which, while helpful for context, could be considered slightly extraneous.

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's complexity (AI-powered image transformation with 7 parameters), no annotations, and no output schema, the description is moderately complete. It covers the core functionality and AI method but lacks important contextual information: what the output looks like (URL? file? format?), error conditions, performance characteristics, or integration notes with sibling tools like 'upload_file'. The mention of 'coming soon' features helps manage expectations but doesn't fully compensate for missing behavioral context.

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 100%, so the schema already documents all parameters thoroughly. The description adds minimal parameter semantics beyond the schema - it mentions 'AI outpainting' which relates to the 'extend' mode and 'background_prompt', and references 'platforms' which maps to 'target_format' enum values. However, it doesn't provide additional context about parameter interactions or usage patterns that aren't already in the schema descriptions.

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's function as 'Resize/reformat images for different platforms' with the specific method 'Uses AI outpainting to intelligently extend content for new aspect ratios.' It distinguishes from siblings like 'upscale_image' (resolution increase) and 'edit_image' (general editing) by focusing on platform-specific resizing with AI extension. However, it doesn't explicitly differentiate from 'inpaint_image' (which might also modify content).

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 context through the phrase 'for different platforms (like Canva Magic Resize)' and mentions alternative modes ('crop' and 'letterbox' coming soon), but it doesn't explicitly state when to use this tool versus siblings like 'compose_images' or 'edit_image'. The note about upcoming modes provides some guidance on current limitations, but lacks explicit when-to-use or when-not-to-use instructions.

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