directus_update_role

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 but provides none. It fails to mention error conditions (e.g., if ID doesn't exist), whether the update is partial or full-replacement, what fields are permissible in the data object, or required authentication levels.

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 brief at only four words, but the '[UNIFIED]' tag wastes space without adding semantic value. While front-loaded, the presence of metadata leakage prevents a higher score for conciseness.

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 the tool has three required parameters including a complex nested object with arbitrary properties, zero schema documentation, and no output schema, the description is severely inadequate. It omits critical information about the flexible data payload structure that would be necessary for successful 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?

With 0% schema description coverage, the description must compensate by explaining the three parameters (site, id, data). It explains none. Critically, the 'data' parameter accepts arbitrary properties (additionalProperties: true), yet the description offers no guidance on valid role fields, expected formats, or required vs optional sub-fields.

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 the basic action ('Update') and resource ('role'), but the '[UNIFIED]' prefix appears to be metadata noise rather than descriptive content. It fails to distinguish this tool from siblings like directus_create_role or directus_delete_role, offering only minimal scope clarification ('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?

No guidance is provided on when to use this tool versus alternatives (e.g., create_role for new roles), nor are prerequisites mentioned (such as admin permissions). The description offers no 'when-not-to-use' constraints or workflow context.

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