directus_get_folder

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

No annotations provided, leaving full burden to description. While 'Get' implies read-only safety, description lacks explicit confirmation, error behavior (404 vs empty), authorization requirements, or return structure disclosure.

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 (one sentence), but the '[UNIFIED]' prefix wastes front-loaded space without adding clarity. Otherwise efficient, though brevity is excessive given zero schema coverage.

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 2-parameter tool with 0% schema coverage. Missing explanation of 'site' parameter semantics, return value structure, and error conditions that would be necessary for confident invocation without output schema or annotations.

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. Description mentions 'by ID' indicating the 'id' parameter purpose, but completely fails to explain the 'site' parameter (e.g., whether it's a site ID, URL, or name), leaving critical parameter semantics undocumented.

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 specific action ('Get') and resource ('folder') with lookup method ('by ID'), distinguishing it from the sibling 'directus_list_folders'. However, the '[UNIFIED]' prefix appears to be metadata noise without explanatory value.

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 sibling alternatives like 'directus_list_folders' or prerequisites such as needing to know the folder ID in advance. No mention of error handling when ID doesn't exist.

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