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

Beyond the readOnly/idempotent annotations, it discloses capacity limits, post-expiry read/export access, non-deletion of files, publish behavior, private no-store responses, and untrusted-text handling. These are substantive operational and security traits an agent would not get from the annotations.

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?

The purpose is front-loaded in the first sentence, but the description then carries many tangential policy details about purchase, upload, replacement, and removal that are not needed to select or invoke a list operation. It is informative but overstuffed for this tool.

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?

It provides substantial context about capacity, privacy, and safety for a simple one-parameter read tool. It does not describe the return shape or pagination behavior, and there is no output schema, but the core invocation context is otherwise complete.

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?

The sole parameter is fully documented in the schema as a continuation cursor, but the description does not mention 'after' or pagination at all. With 100% schema coverage, the schema carries the parameter semantics and the description adds nothing further.

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?

The first sentence states a specific verb and resource plus scope: list bases in the personal account. It implicitly distinguishes personal from team/public listing, but it never names the relevant siblings such as team_list_bases, public_list_bases, or list_followed_bases.

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 description gives no explicit when-to-use guidance or alternatives. It says 'Personal-account operations' but does not explain when to choose this over team_list_bases, public_list_bases, list_followed_bases, or list_collections.

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