directus_get_settings

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It offers no information about authentication requirements, rate limits, caching behavior, or what happens if the site parameter is invalid. The '[UNIFIED]' prefix is unexplained metadata that adds no behavioral clarity.

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 extremely brief (four words plus metadata tag), qualifying as concise. However, the '[UNIFIED]' prefix appears to be implementation metadata that does not help the AI understand tool functionality, representing slight structural noise without value.

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 single-parameter read operation with no output schema, the description should explain both the input parameter and hint at return content. It fails to document the 'site' parameter or indicate what system settings fields might be returned, making it insufficient for confident invocation.

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% for the required 'site' parameter. The description '[UNIFIED] Get system settings' provides no compensation—it does not explain what the 'site' parameter represents (e.g., site ID, URL, name) or its expected format, leaving the parameter effectively 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 a clear verb ('Get') and resource ('system settings'), providing the basic purpose. However, it lacks specificity about what 'system settings' encompasses in Directus and fails to distinguish from the sibling tool 'directus_update_settings', which is critical for selection.

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 is provided on when to use this tool versus alternatives. The description does not mention the existence of 'directus_update_settings' or clarify that this is a read-only operation, leaving the agent without selection criteria.

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