directus_get_file_url

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

No annotations are provided, so the description carries the full burden. It fails to disclose whether the returned URL is public, signed/temporary, or requires authentication headers, nor does it mention cache behavior or error states (e.g., file not found).

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?

Single sentence with minimal bloat (aside from the '[UNIFIED]' tag), but undersized for the complexity. The information density is low given the lack of structured metadata elsewhere.

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?

Inadequate for a tool with 3 undocumented parameters, no annotations, and no output schema. Missing critical context: URL validity duration, authentication requirements, and response format (string vs object).

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%. While the description implies 'id' refers to a file ID, it does not explain what 'site' represents (instance identifier?) or that 'download' triggers a Content-Disposition attachment header versus inline viewing.

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 action (Get) and resource (direct URL to a file), distinguishing it from sibling 'directus_get_file' (content/metadata) and 'directus_import_file_url' (importing). The '[UNIFIED]' prefix is noise but the core purpose is clear.

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 no guidance on when to use this versus 'directus_get_file' (for metadata) or when to set the 'download' parameter to true. No prerequisites or error conditions mentioned.

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