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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds real context on top: results are newest-first, include app links and a public-link flag for docs, and pins reflect what every chat in the space reads, including parent spaces. It stops short of describing page size or termination behavior.

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 main sentence front-loads the payload ('Everything in one space') and the two follow-ups add pagination and pins semantics with no filler. Dense but slightly run-on, with the pins clause tacked on rather than structured.

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 carries the burden of describing return contents, and it does so well: item kinds, ordering, links, and the public-link flag. It could still say more about page size or when next_cursor is absent, but nothing essential for a correct call is missing.

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%, so the baseline is 3, but the description adds meaning beyond the schema by framing cursor as a continuation token ('Pass cursor to read on') and by clarifying that the listing spans parent spaces, which informs how space_id scopes results.

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 description names the resource ('Everything in one space') and enumerates what is returned: docs with their types (doc, deck, storyboard), chats, rolls of images and video, and uploaded assets. It is specific about scope and ordering, but never distinguishes this listing tool from the sibling list_elements, which an agent could plausibly confuse it with.

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?

'Pass cursor to read on' gives clear pagination guidance, and the enumeration implies the tool is for browsing a full space. However, there is no explicit statement of when to choose this over list_elements, list_spaces, or read_doc, and no preconditions for space_id beyond the schema note.

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