directus_list_users

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

No annotations provided, so description carries full burden. Only behavioral clue is 'filtering options'—does not disclose pagination behavior (limit/offset params), return format, or whether results are paginated/complete. Does not mention if this requires admin privileges.

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 is efficient, but '[UNIFIED]' prefix is metadata noise that doesn't aid selection. Description is too minimal given zero schema documentation—it doesn't earn its brevity.

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 6 parameters, 0% schema coverage, no annotations, and no output schema, the description omits critical context: pagination mechanics, 'site' parameter purpose, and what user fields are returned.

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 6 parameters. Description mentions 'filtering options' which loosely implies filter/sort/search, but provides no semantics for required 'site' parameter (unclear if this is tenant, instance, or domain) or pagination parameters (limit/offset).

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 clear verb-resource combo ('List all users in Directus') and mentions 'filtering options' hinting at capabilities. However, fails to differentiate from sibling directus_get_user (single user lookup) or directus_search_items (generic search).

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?

Contains no guidance on when to use this tool versus alternatives like directus_get_user or directus_search_items. No prerequisites or exclusions mentioned.

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