directus_list_operations

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

No annotations provided, so description carries full burden. While 'List' implies read-only, the description fails to disclose return format, pagination behavior (despite limit parameter existing), or whether this retrieves operations across all flows or requires specific flow scoping.

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 appropriately brief, but '[UNIFIED]' tag wastes space without adding value. Given the complete lack of schema documentation, the description is actually too concise—insufficient content for the complexity gap.

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 zero schema descriptions, no output schema, and a complex Directus domain (flows/operations relationships), a single sentence is inadequate. Missing: parameter details, return structure, pagination logic, and relationship to parent flows.

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 with three parameters (site, filter, limit). The description completely fails to compensate—no mention of what 'site' refers to (URL? name?), filter syntax, or that limit defaults to 100. Agent has no semantic guidance for invocation.

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 (List) and resource (operations in flows), distinguishing from sibling directus_list_flows. However, '[UNIFIED]' prefix is metadata noise that doesn't aid understanding, and the description assumes familiarity with Directus 'flows' concept without brief clarification.

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_get_flow, directus_create_operation, or directus_list_flows. No mention of prerequisites like needing flow IDs or permissions.

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