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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds real context beyond that: responses are private, no-store, and uploaded text is untrusted data rather than instructions. The quota, purchase, and publishing sentences are about the product rather than this call, so the added value is diluted but present.

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 one sentence, but eight further sentences cover pricing, quotas, expiry, publishing, and removal policy — almost none of which help an agent call a read-only document list. Signal is buried under boilerplate.

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, the description should explain the shape of the response, but it never says the result is a document list plus a next cursor. Safety and trust context is covered; the return contract an agent needs for pagination is not.

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 coverage is 100% and both parameters (base_id, after) are documented in the schema, so the baseline is 3. The description adds no meaning beyond it — it never mentions cursor pagination or validates the base_id format, leaving the schema to carry the load.

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?

"List the documents in your base" gives a clear verb and resource, and "Personal-account operations" implicitly distinguishes it from the team_* and public_* listing siblings. However, it never names those alternatives (team_list_base_documents, public_list_base_documents, search_base) explicitly, so differentiation is left to inference.

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 "Personal-account operations" is the only routing hint, implying this is not the team or public variant, but no sibling is named and no condition is spelled out. Nothing tells the agent when to prefer search_base or get_base_document instead, so usage is only implied.

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