directus_list_collections

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

No annotations provided, so description carries full disclosure burden. Fails to indicate if read-only (implied by 'List' but not explicit), pagination behavior, return format, or rate limits despite absence of output schema.

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, appropriately front-loaded. '[UNIFIED]' prefix is extraneous metadata but doesn't significantly impede readability. No wasted words.

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 zero schema coverage, no annotations, no output schema, and existence of similarly-named siblings, the description is insufficient. Missing: parameter semantics, return value structure, and differentiation from related list/get operations.

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 has 0% description coverage for the required 'site' parameter. Description offers no compensation—no explanation of what 'site' refers to (instance URL? name?), valid formats, or examples.

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 specific verb 'List' and resource 'collections (tables)' with scope 'all'. Implicitly distinguishes from sibling 'directus_get_collection' (singular) by emphasizing 'all', though explicit distinction would strengthen clarity.

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_collection' (for single collection details) or 'directus_list_items' (for data within collections). No prerequisites or authentication context mentioned.

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