directus_list_roles

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

No annotations provided, so description carries full burden. 'List' implies read-only operation but does not confirm it. No disclosure of pagination behavior, auth requirements, or what constitutes a 'role' in Directus context.

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 after prefix. '[UNIFIED]' tag wastes space without adding semantic value for tool selection. Efficient but underweight given 4 undocumented 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?

Inadequate for complexity level: 4 parameters with 0% schema coverage, no annotations, no output schema. Description covers only basic operation identification, leaving critical implementation gaps (filter syntax, site identifier format, role structure).

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 description to compensate. It mentions none of the 4 parameters (site, filter, sort, limit). The required 'site' parameter and complex filter syntax are left completely 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?

States specific verb (List) and resource (roles) with scope (all). The '[UNIFIED]' prefix is noise, but 'all' implicitly distinguishes from sibling directus_get_role. Lacks explicit differentiation from other list operations like directus_list_users.

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_get_role (single retrieval) or other list operations. Does not mention that filtering is available via the filter parameter or that pagination via limit defaults to 100.

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