directus_get_collection

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

Implies read-only operation via 'Get' and partially discloses return content ('schema and meta information'), but lacks critical behavioral details required given no annotations: no mention of error behavior when collection doesn't exist, authentication requirements, rate limits, or the structure/format 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?

Single sentence is appropriately brief, but the '[UNIFIED]' prefix wastes characters on unexplained implementation metadata rather than functional guidance. Otherwise efficient.

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?

Given zero schema documentation and no output schema, the description inadequately compensates by omitting parameter semantics, error handling, and detailed return structure. Only partially covers what the tool returns.

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?

With 0% schema description coverage, the description must compensate for both 'site' and 'collection' parameters but fails to explain 'site' at all and only implicitly references 'collection' as the target resource without specifying format requirements (name vs ID vs UUID).

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 verb 'Get' and resource 'collection details' and clarifies returned content includes 'schema and meta information.' However, loses one point for the '[UNIFIED]' prefix noise which appears to be implementation metadata without explanation, and it does not explicitly distinguish from sibling directus_list_collections.

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 explicit guidance on when to use this tool versus directus_list_collections or when retrieving a single collection is preferred over listing. No prerequisites or error conditions mentioned.

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