directus_list_comments

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

No annotations provided, so description carries full disclosure burden. '[UNIFIED]' prefix is unexplained noise. No mention of pagination behavior, maximum limits, default sorting, or authentication requirements. Does not confirm read-only nature despite 'List' implying it.

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?

Only one sentence, but '[UNIFIED]' prefix appears to be implementation metadata leaking into the user-facing description, wasting valuable space without adding meaning. Otherwise appropriately brief.

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 4-parameter tool with zero schema documentation and no output schema. Missing essential context: what 'site' refers to, what filtering syntax is supported, and how pagination/limiting behaves. Should explain the '[UNIFIED]' designation or remove it.

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 (4 params with no descriptions). Description fails to compensate by not mentioning any parameters, including the required 'site' parameter or the filter/sort syntax expected. No value added beyond the schema structure.

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?

Provides specific verb (List) and resource (comments). Distinguishes from sibling `directus_create_comment` by action type. However, 'on items' is vague regarding what constitutes an 'item' in the Directus context, missing an opportunity to clarify the scope.

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 provided on when to use this versus other query tools, nor any mention of prerequisites like permissions or valid 'site' identifiers. Zero explicit or implicit usage constraints documented.

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