directus_search_items

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

No annotations provided, so description carries full burden. States 'full-text search' but doesn't disclose pagination behavior, which fields are indexed/searchable, case sensitivity, or return format. No mention of read-only nature.

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 no waste. Front-loaded with the key action. However, extreme brevity is inappropriate given zero schema documentation and 5 parameters.

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?

Five parameters with zero schema documentation require descriptive explanation. Search tools need syntax guidance. No output schema exists, yet description doesn't hint at return structure (array of items, relevance scoring, etc.).

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. Description implies 'collection' and 'query' parameters exist but provides no semantics for 'site' (Directus instance identifier?), 'fields' (return fields vs search fields), or 'limit'. Insufficient compensation for undocumented schema.

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 'search' and resource 'items in a collection'. '[UNIFIED]' prefix is unexplained jargon. Distinguishes functionally from sibling directus_list_items (search vs list) but doesn't explicitly name the alternative.

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_list_items or directus_get_item. No mention of search syntax, wildcards, or prerequisites like collection existence.

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