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

Beyond the readOnlyHint/destructiveHint annotations, the description discloses the important behavioral trait that this reads from a local broker index and never calls Drive, implying possibly-stale cached data. It also tells the agent what the rows carry (selection_key in gdrive: form), which the annotations do not.

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?

Two tight sentences with no filler; the source constraint ('never calls Drive') and the downstream-use hint are both front-loaded and each sentence earns its place.

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 no output schema and no documented parameters, the description covers the read-only nature and row payload adequately but leaves the input contract (especially q and connection_context) entirely unexplained, which is a real gap for a listing tool.

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?

Three parameters (q, limit, connection_context) have 0% schema description coverage, and the description explains none of them - not the query semantics of q, nor the meaning/default behavior of limit, nor the connection_context pattern. The description does not compensate for the schema gap.

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 (List) and resource (Google Drive files/creatives) plus the exact data source (the local broker index), which meaningfully separates it from the broader creatives_list sibling. It stops short of naming that sibling explicitly, so an agent must infer the distinction.

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 rather than stated: it hints that returned selection_key values feed 'create flows', which suggests when the results are useful. There is no explicit when-to-use or when-not-to-use guidance versus creatives_list, creatives_get, or creatives_list_folders.

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