compose_images

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

No annotations are provided, so the description must fully disclose behavior. It only says 'compose' with references and prompt, but fails to explain side effects (e.g., file creation), permission needs, or whether the process is synchronous. This is insufficient for a transformation 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 a single sentence of 20 words, front-loading the key action. Every word is functional, 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 complexity (4 parameters, composition task) and the presence of an output schema, the description should explain the composition process, constraints, or default behavior. It does not, leaving gaps about how images are merged, resolution limits, or effect of the prompt.

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 100% schema coverage, baseline is 3. The description adds minimal value beyond the schema: it repeats that reference images are 1-3 but does not elaborate on model or aspectRatio. No extra context or constraints are provided.

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: composing a new image using reference images and a text prompt. The verb 'compose' and resource 'image' are specific, and it distinguishes from sibling tools like generate_image (no reference images) and edit_image (modifies existing).

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 should be used when 1-3 reference images are available and textual guidance is wanted. However, it lacks explicit when-not-to-use guidance or comparison to alternatives like generate_image or animate_image.

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