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

Annotations already cover the read-only, non-destructive, non-open-world profile. The description adds genuinely new behavioral context beyond them: the binding precondition and the explicit statement that agents cannot perform binding, which prevents a fruitless attempt loop. It does not disclose what 'status' values can be returned.

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 sentences, zero filler, and the more decision-relevant constraint (agents cannot bind) is placed up front. Nothing to trim.

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?

No output schema exists, so the description carries some burden for return values, and it does not say what statuses are reported or what the agent should do with each. Combined with the undocumented connection_context parameter, a small but real gap remains for a tool meant to gate a human-driven workflow.

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?

There is one parameter, connection_context, with 0% schema description coverage and a non-obvious required pattern (mctx_v1_ + 64 hex chars). The description says nothing about what this parameter is, where the agent obtains it, or whether it is optional — leaving the only parameter undocumented in both places.

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: 'Read-only Google Drive library status for the current user.' This is distinguishable from sibling creatives_list_cloud / creatives_list, which deal with creatives rather than Drive binding state. It does not explicitly name a sibling to contrast with, so a 4 rather than 5.

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?

Clearly frames the operational boundary: binding must be done by a human in the browser and agents cannot bind, which tells the agent this tool is for checking state, not changing it. It stops short of naming alternatives (e.g. which tool to call after binding succeeds) or stating when the status is meaningful (pre/post binding).

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