Generate Image Asset

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

The description adds meaningful context beyond annotations: it reveals an external dependency (OPENAI_API_KEY), clarifies the side effect of saving to staging, and states 'Does not publish media.' These details complement the annotations (readOnlyHint=false, destructiveHint=false) without contradiction.

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 sentences long, front-loaded with the core action, and every clause adds relevant information. 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?

For a tool with 11 parameters and no output schema, the description covers the core purpose, key side effects, and dependencies. It could elaborate on failure modes or return format, but the strong schema and annotations mitigate the need for more detail.

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?

The schema already provides detailed descriptions for all 11 parameters (100% coverage), so the description adds limited value for parameter semantics. The mention of returning a local path and manifest metadata provides slight extra context but does not significantly enhance understanding of individual parameters.

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: generating an image via OpenAI, saving it to Context Bridge staging, and returning a local path plus manifest metadata. It also differentiates from siblings by explicitly noting it does not publish media, distinguishing it from publishing/registration tools.

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 provides clear context on what the tool does and highlights the environment requirement (OPENAI_API_KEY). It implies when to use this tool versus publishing tools, but does not explicitly name alternative siblings like register_image_asset for registering existing assets, leaving a small gap.

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