generate_image

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

With no annotations, the description carries the full burden. It discloses that the tool 'Saves the result and returns a file resource,' which is a key side-effect. However, it does not clarify whether the original image is modified, mention any required permissions, rate limits, or provider-specific side effects. The schema provides some provider behavior, but the description adds limited transparency.

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 two concise sentences with no wasted words. It front-loads the purpose and then states the output/side-effect. Excellent structure for quick parsing.

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?

For a complex 11-parameter tool with no output schema, the description provides a high-level purpose and return type but omits prerequisites, error behavior, and provider differences. The extensive schema descriptions fill many gaps, making the description minimally complete for initial understanding, though more context would be beneficial.

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?

All 11 parameters have detailed descriptions in the schema (100% coverage), so the baseline is 3. The tool description itself adds minimal parameter-level meaning beyond referencing inputImagePath for editing. The rich schema descriptions carry the semantic load, and the description does not need to compensate.

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 explicitly states the tool 'Generate a new image from a text prompt or edit an existing image using inputImagePath' and 'Saves the result and returns a file resource.' This is a specific verb+resource with clear scope, distinguishing the two main operation modes. Though no sibling tools exist, the purpose is unambiguous.

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: use this tool to generate from text or edit when an inputImagePath is provided. It clearly indicates the editing condition by referencing inputImagePath. However, it does not explicitly provide when-not-to-use guidance or name alternatives, though the schema descriptions further clarify parameter-specific usage.

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