prepare_image

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

With no annotations provided, the description carries the full burden. It discloses the behavior: returns guidance, recommendations, and a polished prompt. It sets expectations about the purpose (avoid wasted calls). It does not mention side effects, but for a guidance tool this is less critical.

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?

Two sentences, front-loaded with the primary action ('Get guidance before generating an image'). Every sentence earns its place, including the explicit 'Call this FIRST' instruction and the benefit statement.

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 simple tool with two optional params and no output schema, the description covers the essential context: purpose, timing, outputs, and rationale. It is complete for an agent to decide when and how to invoke it.

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 coverage is 100% for the two optional parameters, so the baseline is 3. The description adds minor context by mentioning 'prompt recommendations' and 'polished version', but does not provide syntax or format details beyond what the schema already includes.

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 verb and resource: 'Get guidance before generating an image.' It distinguishes itself from siblings by positioning as a pre-generation step ('Call this FIRST') and describing specific outputs (supported parameters, prompt recommendations, polished prompt).

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?

It explicitly instructs to 'Call this FIRST' and explains the context (before generating an image) and benefit (avoids rejected generations). However, it does not explicitly name alternatives or state when not to use, though the sibling names imply generation vs. preparation.

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