list_space_files

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

No annotations are provided, so the description must carry full weight. It claims to list 'all files', yet the page_size parameter limits scanning to a specific number of messages, creating potential confusion. It also does not disclose whether the operation is read-only, what permissions are required, or how Drive attachments and shared URLs are handled.

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 description is a single sentence that efficiently conveys the core function without unnecessary words, though it could benefit from slight structural improvements to denote limitations.

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 and no annotations, the description should provide more context about return format, default behavior, and any limits. It fails to mention that returned files may be only those in recently scanned messages, leaving the agent without crucial operational 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?

All three parameters (group_id, is_dm, page_size) have descriptions in the input schema, which already explains their meaning. The tool description adds no additional semantic value for these parameters beyond what the schema provides.

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 clearly states the verb 'List' and the resource 'all files, Drive attachments, and shared URLs', and specifies the context 'in a space or DM', which distinguishes it from sibling tools that handle messages, reactions, or statuses.

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 tool's purpose is implied by its name and description, but there is no explicit guidance on when to use it versus alternatives like search_messages for finding specific file references, or why someone might choose not to use it (e.g., if only recent files are needed).

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