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

No annotations are provided, so the description carries the burden, and it does disclose real behavior: deterministic ordering (folders by position then name, files by name) and the return shape (folders[], files[] containing cuids usable with get_file/delete_file). It omits pagination, size limits and permission/auth requirements, which keeps it short of a 5 for an unannotated tool.

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?

Three sentences, front-loaded with purpose, then return shape, then the one non-obvious parameter behavior. No filler, and each sentence carries information an agent needs.

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 3-parameter read tool with no output schema and no annotations, the description supplies both the return structure and the root-vs-subfolder semantics an agent needs to call it correctly. Missing only peripheral items such as pagination and auth expectations.

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 100%, so all three parameters are already documented, including the org-prefixed slug form and the null-means-root default. The description largely restates the parent_folder_id default rather than adding new syntax or format detail, so the baseline 3 applies.

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 and resource ('List the folder + file children of a Files surface') and scopes it with kind='files', which separates it from list_recent_files, list_surfaces and the get_file/delete_file siblings it names. An agent can tell what this returns and what it does not without opening the schema.

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?

Gives explicit invocation context: parent_folder_id defaults to null meaning surface root, pass a folder id to descend, and use list_surfaces to enumerate surfaces. It stops short of an explicit 'use this instead of list_recent_files when...' exclusion, so it is clear context rather than full routing guidance.

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