directus_list_items

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

No annotations provided, so description carries full burden of behavioral disclosure. While 'List' implies read-only operation, the description fails to confirm safety, disclose response format, pagination limits, or error behavior for invalid collections.

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 with zero waste. Information is front-loaded with the '[UNIFIED]' tag followed by clear action statement. However, given zero schema documentation and no annotations, this level of brevity constitutes under-specification rather than optimal conciseness.

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?

Inadequate for an 8-parameter tool with 0% schema coverage and no output schema. The description compensates for neither the undocumented parameters nor the missing return value documentation. Mutation implications and error cases are not addressed.

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%, requiring substantial description compensation. While 'filtering, sorting, and pagination' conceptually maps to filter/sort/limit/offset parameters, critical parameters (site, fields, search) lack any explanation, and data formats for filter strings remain undocumented.

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?

Provides specific verb (List), resource (items from Directus collection), and scope (any collection with filtering/sorting/pagination). The '[UNIFIED]' prefix hints at generic applicability but fails to explicitly differentiate from sibling tools like directus_search_items or directus_get_item.

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 on when to use this versus directus_search_items or directus_get_item. No mention of required parameters (site/collection) prerequisites or when to prefer this over collection-specific listing tools.

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