directus_list_panels

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

With no annotations provided, the description carries the full burden but fails to disclose read-only safety, return format, pagination behavior, or rate limits. The mention of filtering is the only behavioral detail beyond the basic operation type.

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 description is appropriately brief and front-loaded, though the '[UNIFIED]' prefix is unnecessary metadata noise that doesn't aid comprehension.

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 zero schema descriptions and no output schema, the description is insufficient. It fails to explain what attributes panels have, what the filter syntax expects, or how pagination works despite the presence of a limit parameter.

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%, yet the description inadequately compensates. While 'filtered by dashboard' hints at the filter parameter's purpose, it doesn't clarify the expected format (ID vs name), explain the required 'site' parameter (instance identifier), or describe the 'limit' parameter's pagination semantics.

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 clearly states the verb (List) and resource (panels), distinguishing it from sibling operations like directus_create_panel and directus_delete_panel. However, it assumes familiarity with Directus dashboard panels rather than explaining what a 'panel' is.

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?

The phrase 'optionally filtered by dashboard' implies usage context (filtering by dashboard), but provides no explicit guidance on when to use this versus directus_get_dashboard or directus_list_dashboards, nor when filtering is preferable.

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