directus_get_version

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

No annotations are present, placing full burden on the description. The description provides no information about auth requirements, rate limits, error handling (404 behavior), return payload structure, or whether this operation is read-only (implied by 'Get' but not explicit).

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?

Very brief single sentence. While efficiently short, the '[UNIFIED]' prefix adds no semantic value for tool selection and constitutes noise. The core message is front-loaded but lacks supporting detail.

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?

Severely incomplete given zero annotations, 0% schema coverage, no output schema, and two undocumented required parameters. For a retrieval tool in a versioning system, the description lacks critical context about the versioning model and parameter semantics.

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 description coverage is 0%, requiring the description to compensate. While 'by ID' hints at the id parameter, it offers no explanation of what 'site' refers to (instance/site identifier), expected ID format, or that both parameters are required. The parameter semantics are largely 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?

The description states the basic action (Get) and resource (version details) and mentions the ID filter. However, it fails to clarify what 'version' refers to in the Directus context (content versioning vs API versions) and does not distinguish from sibling directus_list_versions, leaving ambiguity about when to use single retrieval versus listing.

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 tool versus directus_list_versions or other version-related operations. No mention of prerequisites, error conditions (e.g., invalid ID), or workflow context.

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