generate_image_with_shared_context

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only mentions high-level capabilities ('supports all four models', 'supports specifying resolution') and style consistency but omits critical behavioral details like what the tool returns, whether it saves files, error handling, rate/concurrency implications, or side effects. This is insufficient for an agent to safely invoke the 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, concise line with an emoji and bold text. Every segment adds value: purpose, style consistency, target use cases, model support, and resolution support. There is no fluff or redundancy, making it highly efficient.

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?

This is a complex batch tool with 7 parameters, 2 required, and no output schema. The description gives high-level use cases but omits essential details about how the shared context is applied, how the requests array should be structured, what the output looks like, and potential side effects. For an agent to confidently use this tool, significantly more context is needed.

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 description coverage is 100%, so the baseline is 3. The description's mention of shared context and resolution aligns with the styleContext and resolution/image_size parameters, but it does not add new semantic meaning beyond what the schema already provides. No extra parameter guidance is given.

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 '共享上下文批量生图' (shared-context batch image generation) and '保持风格一致性' (maintaining style consistency), specifying the action and distinguishing value proposition. It also gives concrete use cases (PPT, tutorials, card sets) that set it apart from generic batch generation. However, it does not explicitly name or contrast sibling tools like generate_image_batch, so it falls short of a full 5.

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 usage context: suitable for series images such as PPT, tutorials, and card sets, implying the need for consistent style. It does not explicitly state when not to use this tool or mention alternatives, so it lacks the exclusion and alternative guidance needed for a 5. Still, the use-case framing is directly actionable.

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