directus_list_folders

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

With no annotations provided, the description carries full burden but discloses almost nothing beyond the basic read operation. It does not clarify return format, pagination behavior, rate limits, or whether 'all' implies unbounded retrieval or respects the limit parameter.

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 brief but wastes the opening on '[UNIFIED]' metadata without explanation. While not bloated, the single sentence fails to front-load actionable guidance given the parameter complexity.

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 tool with 5 parameters (including filtering, sorting, and pagination) and no output schema, the description is severely inadequate. It lacks return value hints, error scenarios, or examples despite the high parameter count and zero schema documentation.

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 coverage is 0% and the description fails to compensate. Critical parameters like 'site' (required) receive no explanation, and filtering/sorting syntax (string types) are undocumented. The user has no guidance on valid filter formats or sort keys.

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 identifies the action ('List') and resource ('folders in Directus storage'), distinguishing it from sibling tools dealing with files, items, or collections. However, it fails to differentiate from directus_get_folder (single retrieval) versus this list operation.

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_folder, when to apply filters versus retrieving all, or how to handle pagination. No prerequisites or authentication context is mentioned.

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