ensure_brand_consistency

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

No annotations are provided, so the description carries full responsibility for explaining behavior. It says the tool 'analyzes and refines' assets, but does not clarify whether it modifies input files, creates new assets, returns analysis results, or requires persistence. The mention of identity preservation is helpful but still leaves significant behavioral gaps.

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 short and reasonably structured, with the primary purpose stated first and the mechanism second. 'Nano Banana Pro' is somewhat marketing-oriented but not excessive. No redundant or filler content is present.

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?

With five parameters, no output schema, and no annotations, the description leaves too much unstated. It does not specify what the tool returns, whether assets are modified in place, what happens to non-conforming assets, or which inputs are required beyond the schema defaults. An agent would struggle to call this tool confidently without further guidance.

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%, so the input schema already documents all five parameters. The description references brand guidelines and consistency but adds no parameter-specific details beyond what the schema already states. A baseline score of 3 is appropriate.

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: analyze and refine assets to follow brand guidelines. It mentions using Nano Banana Pro's identity preservation for multi-image consistency, which helps distinguish it from the generation-focused siblings. However, it does not explicitly differentiate itself from 'edit_asset', which could also refine assets.

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 no explicit guidance on when to use this tool versus generate_asset, generate_asset_pack, or edit_asset. The intended use case is implied from the tool name and opening sentence, but there is no mention of alternatives or conditions that would make this tool the right choice.

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