directus_list_policies

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention pagination behavior, rate limits, or what data the policies contain. The claim to list 'all' items while having a limit parameter is misleading.

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?

The single sentence is brief, but '[UNIFIED]' appears to be metadata noise that doesn't help the LLM. The claim of listing 'all' items is structurally misleading given the limit parameter, meaning the sentence doesn't efficiently earn its place.

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?

Given 3 undocumented parameters, no annotations, and no output schema, the description is severely incomplete. It lacks explanation of the Directus-specific concept of policies, return value structure, and proper parameter guidance.

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?

With 0% schema description coverage across 3 parameters (`site`, `filter`, `limit`), the description must compensate by explaining parameter semantics. It adds no information about what `site` refers to (URL? name?), the format of `filter` (JSON? query string?), or the pagination logic of `limit`.

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?

The description identifies the action (List) and resource (access policies), but the word 'all' contradicts the `limit` parameter (default 100). It also fails to distinguish 'policies' from the sibling tool `directus_list_permissions`, which is critical in Directus where these are distinct concepts.

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 tool versus `directus_list_permissions` or other Directus list operations. No mention of prerequisites like authentication or required permissions for viewing policies.

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