directus_get_server_info

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

No annotations are provided, so the description carries the full burden. It mentions retrieving version and extensions but fails to disclose if this is a read-only operation, whether it requires authentication/authorization, rate limits, or the structure of the returned data.

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 a single, front-loaded sentence with no redundancy. However, given the complete lack of parameter documentation and behavioral context, this represents under-specification rather than efficient communication.

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?

For a tool with one required parameter and no output schema, the description is inadequate. It covers the high-level purpose but omits critical invocation details (parameter semantics, return structure), forcing the agent to guess how to use the tool.

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?

The input schema has 0% description coverage for the required 'site' parameter. The description completely fails to compensate by not mentioning the parameter at all, leaving the agent with no information about what 'site' represents (URL, ID, etc.) or its expected format.

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 uses a clear verb ('Get') and resource ('Directus server information'), with specific examples (version, extensions). The '[UNIFIED]' prefix is extraneous but harmless. It implicitly distinguishes from siblings like 'directus_health_check' or 'directus_get_settings' by focusing on server metadata rather than health or application settings.

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 tool versus alternatives like 'directus_health_check' or 'directus_get_settings'. No mention of prerequisites, required permissions, or authentication context.

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