directus_list_permissions

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

No annotations provided, so description carries full burden. Despite 'limit' parameter suggesting pagination, description doesn't disclose pagination behavior, return format, or whether this operation is read-only. '[UNIFIED]' tag hints at implementation detail but offers no behavioral transparency.

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?

Extremely brief (4 words), but '[UNIFIED]' prefix wastes space without adding value for tool selection. While not bloated, extreme brevity results in underspecification rather than efficient communication.

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 a 3-parameter listing tool with filtering capabilities. No output schema exists to explain return values, and description doesn't explain what constitutes a 'permission' object or the difference between null and provided filter values.

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 description coverage is 0% and description fails to compensate. The required 'site' parameter (likely indicating which Directus instance) has no explanation. 'Filter' syntax and 'limit' constraints (max values, pagination) are completely undocumented in both schema and description.

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 basic verb ('List') and resource ('permissions') but lacks specificity regarding scope (system-wide vs user-specific) and fails to differentiate from siblings like 'directus_get_permission' or 'directus_get_my_permissions'. The '[UNIFIED]' prefix is unexplained metadata that doesn't clarify purpose.

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 filtered searches or specific permission retrieval. No mention of prerequisites, required permissions to call this endpoint, or typical use cases.

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