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

Annotations already cover the safety profile (readOnlyHint, destructiveHint, openWorldHint), and the description's "No writes" is largely redundant with that. It does, however, add real behavioral detail beyond the annotations: thumbnail_url is "short-lived" and only present "when ready", which tells the agent the URL may be absent or expire and shouldn't be cached.

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?

One front-loaded sentence with no filler; the key format and identity of the tool are stated first. The trailing clause "with folder_path and a short-lived thumbnail_url when ready" is slightly compressed/telegraphic but still parses.

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 an output schema present, return shape needn't be spelled out, and the tool is a simple single-item read with annotations covering risk. The only real gap is the undocumented connection_context parameter, which matters little given the description otherwise scopes the call precisely.

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 carries the burden; it partially compensates by giving selection_key a format hint ("gdrive:...") and its provenance, but the second parameter connection_context is never mentioned. Partial coverage of a two-parameter tool warrants a middling score.

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 cardinality ("Read one creative") plus the lookup key, and names its sibling source ("from creatives_list"), which cleanly separates it from the list variant. The additional payload facts (folder_path, thumbnail_url) tell the agent what it gets back.

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 phrase "from creatives_list" implies the workflow: enumerate with creatives_list, then fetch one by the resulting key. "No writes" implicitly rules out mutation use, but there is no explicit when-not or alternative named (e.g. when to use creatives_list instead of this).

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