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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and nothing is contradicted. The description adds only the 'opaque' qualifier on the ref; it says nothing about ref expiry, error behaviour for invalid refs, or auth/connection requirements, which is the kind of context that would raise this score.

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?

A single front-loaded sentence with no filler; the key qualifier (where the ref comes from) arrives immediately after the verb-resource statement.

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 low-complexity, read-only getter with annotations covering safety and no output schema to explain, the description supplies the essential prerequisite linkage. Missing details are minor: the undocumented connection_context parameter and any note on ref validity/expiry.

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 compensate. It does explain task_ref meaningfully (opaque, sourced from the list tool), but the second parameter, connection_context, is left completely undocumented in both schema and description, so compensation is only partial.

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 (get) and resource (one task), and identifies the identifier's origin ('returned by google_ads_tasks_list'), which separates it from the sibling list tool. It stops short of contrasting with other single-object readers like tasks_get_status or google_ads_mutation_receipt_get.

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 implied through the phrase 'returned by google_ads_tasks_list', telling the agent this tool runs after a list call. There is no explicit statement of when to prefer it over tasks_get_status or what to do when a task_ref is stale, so guidance remains inferential.

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