directus_get_role

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

No annotations provided, so description carries full burden of behavioral disclosure. Description does not indicate this is a read-only operation, what role object fields are returned, error behavior if ID doesn't exist, or required authentication/authorization level.

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?

Extremely brief at one sentence. '[UNIFIED]' prefix appears to be metadata noise rather than useful descriptive content. Otherwise efficient, but may be too terse given lack of supporting schema/annotations.

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?

Tool has 2 required parameters with 0% schema coverage, no output schema, and no annotations. Description fails to compensate for these gaps by explaining the role data structure, return format, or parameter semantics beyond the minimal 'by ID' hint.

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 for both 'site' and 'id' parameters. Description only implicitly references the 'id' parameter via 'by ID' but provides no format guidance. The 'site' parameter (likely Directus instance identifier) is completely undocumented in both schema and description.

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 'role details' with scope 'by ID'. Distinguishes from sibling directus_list_roles (list vs single get) and directus_get_user_role (getting role assigned to user vs role by ID). '[UNIFIED]' prefix is noise but doesn't obscure clarity.

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 versus alternatives like directus_list_roles (when you don't know the ID) or directus_get_user_role (when you need a user's role). No mention of prerequisites or permissions needed to read roles.

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