Create image

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

Annotations indicate a non-readonly, non-destructive operation, but description provides no additional behavioral details (e.g., output format, file handling, async behavior). Relies on schema defaults that are not explained.

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 extremely short but poorly written ('Create image Creates...'), lacks structure, and fails to convey essential information. It is under-specified rather than concise.

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 (25 parameters, no output schema), the description is grossly insufficient. It does not explain return values, supported operations, or how to use the many optional fields.

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 only 24% schema coverage and 25 parameters, the description adds no information beyond the schema. No parameter semantics are explained, leaving the agent to guess about optional parameters like 'n', 'size', 'quality', etc.

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?

Description repeats the name 'Create image' and says 'given a prompt' but does not specify what kind of image file is created or how it differs from sibling tools like 'create_image'. It is a near-tautology with no differentiation.

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?

No guidance on when to use this tool versus alternatives (e.g., 'create_image', 'edit_image'). Missing context about preferred use cases or limitations.

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