Workspace List Files

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: it auto-paginates through every page and returns entries aggregated from all pages with a null nextPage/hasMore=false. That auto-pagination trait materially changes how an agent should treat the result.

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 core purpose and filters are front-loaded in one short sentence. The second sentence is somewhat convoluted ('Sigma's page', 'Sigma's value') but is dense with useful pagination semantics rather than filler.

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 an output schema present, the return-value explanation is partly redundant, but the auto-pagination disclosure is information the agent needs for correct invocation. Given only two optional params, the definition covers what is needed to call it correctly.

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%, so the description must carry the load, and it does: it names both filters and enumerates the accepted type values ('workbook', 'folder', 'data-model', 'template'). It stops short of describing ID format or default/list-all behavior when both are omitted.

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 files/folders') and enumerates the filterable entity types. It does not explicitly distinguish itself from the close sibling workspace_list_all_files, so the agent must infer the scope difference.

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?

Explains the optional filtering dimensions (parentId, type) which implies usage, but never states when this tool should be chosen over workspace_list_all_files, workspace_list_recent_files, or workspace_list_member_files. No exclusions or prerequisites are given.

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