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

Goes well beyond annotations by disclosing the model (Nano Banana 2 Lite), cost (1 credit), synchronous execution with typical ~10–30s latency, that the asset URL is returned in the result, that results land in the studio gallery, and how keepers reach the vault. This is exactly the operational context annotations cannot convey.

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?

Front-loaded with the key operation, model, cost, and sync behavior before the usage guidance. Dense but nearly every clause carries signal; only the vault-promotion note is somewhat peripheral to calling the tool.

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?

No output schema exists, and the description compensates by saying the asset URL is in the result and where the asset is stored. Combined with annotations covering the mutation profile, an agent has enough to invoke correctly, though aspectRatio guidance would complete 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 description coverage is 0%, so the description must carry parameter meaning. It does this well for prompt and referenceImages (up to 4, https or data URLs, suggested uses), but aspectRatio's enum and influencerId's UUID format/role get no explanation, leaving two of four params undocumented anywhere.

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?

States a specific verb+resource ('Generate ONE on-identity image of an influencer') and implicitly separates itself from siblings like studio_generate_image or seedance_generate_image by calling out the server-side character reference injection that makes the output on-identity. An agent can tell this is the influencer-scoped generator.

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 gives strong intra-tool guidance ('describe the SCENE, outfit, or action, not the person') and clarifies how referenceImages are used, but never states when to prefer this over adjacent tools such as generate_influencer_look or studio_generate_image. Usage context is implied rather than compared against alternatives.

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