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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds the concrete consequence that existing target-language edits can be overwritten, plus the quota constraint ('translation allowances'). That is real behavioral context beyond the hints; it only stops short of describing partial-failure behavior or what the response contains.

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?

Three short sentences, front-loaded with the action, then the risk warning, then the constraint. Every sentence carries distinct information and none repeats the schema or annotations verbatim.

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 destructive mutation with an output schema present, the description covers action, overwrite risk, and quota limits. The remaining gap is behavioral detail on partial success across multiple target languages, which is a minor omission given full schema coverage and an output schema.

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% and the schema already documents the projectId/generationId aliasing, variantId defaulting, and language-code format with the 'unsupported codes are rejected' note. The description's 'requested languages' restates targetLanguages without adding syntax or constraints, so baseline 3 applies.

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?

Specific verb pair (creates/refreshes) plus a specific resource (translated social-graphics layouts) and the mechanism (text translation). That is enough to separate it from translate_layouts, translate_store_listing, and translate_promo_video by resource type, though it never names those siblings explicitly.

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?

Usage is only implied: it's the tool to call when you want social graphics rendered in other languages. There is no explicit guidance on when to prefer it over translate_layouts or list_graphics_translations, and no stated prerequisites (e.g. needing an existing graphics variant).

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