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

Annotations already declare readOnly, non-destructive, and closed-world, so the safety profile is covered. The description adds billing/quota behavior (owner pays ordinary usage; recovery available after exhaustion), which is genuine context beyond the annotations, though it is vague about what 'exhaustion' and 'bounded' actually mean and says nothing about result ordering or page limits.

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 a single efficient sentence, but the second sentence is dense, jargon-heavy, and of unclear relevance to an agent deciding to call the tool, so it does not fully earn 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?

An output schema exists so return values need not be explained, but for a three-parameter listing tool with no schema descriptions, the definition still omits what 'retained files' means, how to obtain a space_id, and what happens at end of pagination. An agent would have to guess at key invocation details.

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% for all three parameters. The word 'Page' implies cursor-based pagination, but space_id (which Space, what format) and limit (max 50) are never explained in the description, leaving the schema as the only source of bare types and patterns.

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 gives a specific verb (page/list), resource (retained files) and scope (one authorized private Space), which distinguishes it from siblings like private_space_file_get or private_space_file_copy. The second sentence about billing and recovery does not clarify the purpose and slightly muddies an otherwise crisp statement.

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?

There is no guidance on when to choose this over private_space_file_get (single file) or private_space_full_history_search. The only contextual note is a cryptic remark about owner-paid usage and 'bounded existing-data recovery ... after exhaustion', which hints at a quota condition but never states a use case or prerequisite.

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