superchat_list_files

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

The annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral details beyond that: it returns only one page, never downloads file contents, and supports pagination via after/before cursors. These traits help an agent predict exactly what will happen when invoking the 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?

The description is two sentences with no wasted words. It front-loads the core purpose, then clarifies key constraints (no download, one page, pagination). Every sentence earns its place.

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 read-only paginated list tool with rich annotations and fully documented parameters, the description is complete. It covers the essential behavior, pagination mechanics, and a critical non-download caveat. The absence of an output schema is acceptable here because the description already sets expectations around metadata and pagination.

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%, and the schema thoroughly documents after, limit, and before. The description reinforces the pagination semantics by mentioning after/before and one-page behavior, but it does not add substantial meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 states a specific verb ('List'), a clear resource ('metadata for files already uploaded to Superchat'), and a scope ('one page'). It also differentiates itself from content-download operations by explicitly saying it does not download file contents, making it easy to distinguish from sibling tools like superchat_get_file.

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 description provides clear operational guidance: use file IDs for message attachments, use after/before for pagination, and expect only one page per call. It does not explicitly name an alternative tool or state when not to use it, but the pagination and no-download context effectively conveys the intended usage.

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