List Files (Dalux Box)

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds that it returns metadata only, supports incremental listing, and can fetch a single file's metadata with fileId. This provides useful behavioral context beyond annotations.

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 extremely concise: two sentences plus a standalone 'Incremental list.' Every word adds value with no redundancy.

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 listing tool with 5 parameters and no output schema, the description adequately explains the tool's behavior: what it lists, the metadata returned, the ability to fetch a single file, and pagination. Combined with schema descriptions for maxPages and pageLink, the agent has sufficient information to use the tool 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?

The description adds meaning to parameters beyond the schema: it explains that fileId retrieves a single file's metadata, and ties maxPages/pageLink to incremental listing. Schema coverage is 60%, and description compensates for the undocumented fileAreaId and enhances understanding of pagination.

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 it lists files within a file area or fetches one file's metadata using fileId, and specifies what data is returned (name, revision ids, properties, folder, deleted status). It distinguishes from dalux_download_file by noting it is metadata only, making the purpose unambiguous.

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 explicitly tells when to use dalux_download_file for content instead of this tool. It does not explicitly exclude other listing tools (e.g., dalux_list_folders), but the focus on files is clear from the name and context.

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