directus_list_versions

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

No annotations provided, so description carries full burden. While 'List' implies read-only behavior and 'drafts' clarifies scope, it omits critical safety confirmations (readOnly/destructive hints), pagination behavior, and return structure.

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?

Extremely brief at 6 words. The '[UNIFIED]' prefix is structural metadata that adds no semantic value for tool selection. Front-loaded action verb is good, but brevity crosses into under-specification.

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?

With 0% schema coverage, no output schema, no annotations, and 4 parameters (including complex anyOf types), the 6-word description is woefully inadequate to understand tool behavior or required inputs.

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% with 4 undocumented parameters. Description completely fails to compensate—no mention of 'site' (required), 'filter' syntax, 'sort' options, or 'limit' pagination constraints.

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 'content versions', and clarifies these include drafts. Implicitly distinguishes from sibling directus_get_version (singular) by using plural 'versions' and list semantics.

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 provided on when to use this versus directus_get_version (fetch specific), when filtering is appropriate, or prerequisites beyond the required 'site' parameter.

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