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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description's useful addition is the returned field set (id | name | file/folder | size | updated), but it says nothing about ordering, pagination, or result limits for large folders.

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?

One tight sentence with the scope first and the returned columns in a compact parenthetical; nothing is wasted. The pipe-delimited return list is slightly telegraphic but readable.

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?

For a simple three-parameter read tool with full schema coverage and complete annotations, the only thing a description must add is the return shape, which it does since no output schema exists. Missing ordering/pagination notes keep it from being fully 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?

Schema coverage is 100%, so all three parameters (spaceId, folderId, spaceType) are already documented in the schema. The phrase 'in a space or in one folder of it' reinforces that folderId is optional and scoped to a space, but adds no format or default detail beyond the schema's 'default the top level'.

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 ('List') and resource ('files and folders') plus the scope hierarchy ('in a space or in one folder of it'). It does not distinguish itself from close siblings such as list_recent_files, search_files, or get_file_details, so an agent cannot route purely from this sentence.

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 scope wording implies 'use this to browse a space or folder contents,' but there is no explicit when-to-use versus search_files or list_recent_files, and no stated prerequisites beyond what the schema's spaceType enum conveys.

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