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

Adds substantial behavior beyond annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false): the write-scope auth requirement, the budget hold-and-release cost semantics, and the licensing/attribution obligation ('credit it when attributionRequired is true'). These are exactly the operational facts an agent needs and are not derivable from structured fields.

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 dense sentences, front-loaded with the core action and value, then licensing, then cost/scope. No filler, though the 'Free:' lead-in to the budget sentence reads awkwardly and forces a re-read of the pricing claim.

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?

An output schema exists, so return values need no explanation, and the description covers auth scope, cost behavior, and licensing. The main omission is explicit routing guidance versus generate_image/find_footage, which is the one thing an agent still has to guess.

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 schema already documents query, source, variant, budgetUsd, and orientation in detail. The description only restates the budget default/max already in the schema and adds no new syntax or format guidance, so the 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?

States a specific verb and resource ('Fetch one licensed real photograph ... or a blank meme template into the media library as a media key'), naming the value produced. It is clearly distinguishable from generation siblings (generate_image, generate_footage) and video siblings (find_footage) by the 'real, licensed' qualifier.

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?

Implied usage is present: this is for real licensed stock/Pixabay photos or meme templates rather than generated content, and the source enum contextualizes the choice. However, it never explicitly says when to choose this over generate_image or find_footage, nor any exclusion conditions, so the agent must infer the routing.

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