directus_get_item

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

No annotations provided, so description carries full burden. Fails to disclose read-only nature, error behavior when ID doesn't exist, return structure, or the significance of the '[UNIFIED]' prefix regarding cross-site behavior.

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 concise, but the '[UNIFIED]' prefix is cryptic noise without explanation. Front-loading is adequate but content is insufficient for the complexity of 4 undocumented parameters.

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?

Lacks output schema and return value description. With 4 parameters at 0% schema coverage and zero annotations, the description inadequately covers the tool's contract. Missing error cases and authentication requirements.

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 getting by 'ID' and from 'any collection', implicitly covering the `id` and `collection` parameters. However, it completely omits the required `site` parameter (crucial for multi-site contexts) and the optional `fields` parameter for projection.

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), resource (single item), and method (by ID from any collection). However, it fails to explicitly distinguish from sibling `directus_list_items` (which retrieves multiple items) or clarify when ID lookup is preferred over searching.

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 on when to use this versus alternatives like `directus_list_items` or `directus_search_items`. Does not mention that the ID must be known beforehand or what to do if the ID is unknown.

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