directus_import_file_url

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention whether the import is synchronous, what happens on duplicate files, whether the original URL is preserved as metadata, or what the return value contains (no output schema exists).

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 (single sentence) and front-loaded with the action verb. However, given the 0% schema coverage and mutation complexity, this brevity results in underspecification rather than efficient communication.

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 mutation tool with 3 undocumented parameters, no annotations, and no output schema, the description is inadequate. It lacks critical context: return value structure, error conditions, side effects on existing files, and the purpose of the 'data' parameter.

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%, requiring the description to compensate. It fails to do so: 'site' (likely instance identifier) and 'data' (unknown purpose - metadata? folder info?) are completely undocumented. Only 'url' is implicitly referenced by the description text.

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 action (Import) and resource (file from URL into Directus storage). While the '[UNIFIED]' prefix is metadata noise, the core sentence effectively distinguishes this from sibling tools like directus_get_file_url by specifying the external-to-internal import direction.

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?

No guidance is provided on when to use this versus alternatives (e.g., directus_upload_file or directus_create_item), nor are prerequisites like authentication, URL accessibility requirements, or supported file formats mentioned.

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