directus_get_user_role

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

No annotations are provided, so the description carries the full burden. While 'Get' implies a read-only operation, there is no disclosure of error behavior (e.g., what happens if the user ID is not found), return format (role object vs. role name), or authentication requirements.

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 efficient sentence, but given the 0% schema coverage and lack of annotations, this brevity is insufficient. The '[UNIFIED]' prefix adds 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?

With 2 undocumented parameters, no output schema, and no annotations, the description leaves critical gaps. It does not explain the relationship between users and roles or the expected response structure, which is necessary context for a lookup tool in a complex CMS API like Directus.

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 both 'site' and 'id' parameters. The description completely fails to compensate by not explaining that 'id' refers to the user ID, what format is expected, or what the 'site' parameter represents (e.g., Directus instance identifier).

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 a specific verb ('Get') and resource ('role') with scope ('of a specific user'). However, it does not explicitly differentiate from siblings like 'directus_get_user' (which returns user details potentially including role) or 'directus_get_role' (which gets a role by role ID).

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_get_user' or 'directus_list_roles'. No mention of prerequisites such as authentication or required permissions.

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