directus_export_items

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

No annotations are provided, yet the description omits crucial behavioral details: whether export generates a server-side file, returns a download URL, or streams data inline; supported formats (CSV/JSON); and whether this operation is idempotent. 'Export' implies side effects (file creation) that are not disclosed.

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 technically concise at one sentence, but the '[UNIFIED]' prefix appears to be implementation metadata rather than descriptive content. For a 6-parameter tool, the brevity constitutes under-specification rather than efficiency.

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?

Severely incomplete for a data export tool with zero schema coverage and no output schema. Missing: export format specifications, pagination/limit behavior (default 1000 is undocumented), filter operators, and authentication/authorization requirements.

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?

With 0% schema description coverage, the description must document the 6 parameters, but only vaguely alludes to 'filtering options' without explaining the filter syntax, field selection format, sort syntax, or the 'site' parameter's purpose. Fails to compensate for the schema's lack of descriptions.

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 the core action (Export) and resource (items from a collection) clearly, but fails to distinguish from siblings like directus_list_items or directus_search_items. Export implies file generation, which is behaviorally distinct from listing, yet this critical distinction is unmentioned.

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 prefer this over directus_list_items (API response) versus export (file download), nor any prerequisites or constraints. The single sentence offers no decision framework.

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