Download File (Dalux Box)

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds significant behavioral context: 'Text-like content returned as UTF-8, everything else base64' and 'Capped at 2 MB by default (maxBytes up to 20 MB)'. No contradictions; these details go 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?

Two sentences, no wasted words. Front-loaded with verb and resource. Clear and efficient.

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?

Given 5 parameters and no output schema, description explains encoding and size limits which are critical for usage. It could mention the return format more explicitly (e.g., 'returns file content as string'), but the disclosure of binary vs text handling is adequate. Lacks some parameter details but overall complete for a download tool.

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 only 20% (only projectId has a description). The overall description does not add meaning to individual parameters. With low schema coverage, description should compensate but does not address the four undocumented parameters (fileId, maxBytes, fileAreaId, fileRevisionId).

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?

Description clearly states 'Download the content of a specific file revision', specifying verb and resource. It distinguishes from siblings like dalux_list_files (which lists files) and dalux_upload_file (which uploads).

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?

Provides explicit guidance: check file size via dalux_list_files first for large drawings/models, and mentions default cap of 2 MB with maxBytes up to 20 MB. This helps the agent decide when to use the tool and how to handle large files, though no explicit when-not-to-use statements.

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