directus_get_permission

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

No annotations provided, so description carries full burden. 'Get' implies read-only, but fails to disclose error behavior (e.g., what happens if ID not found), authentication requirements, or whether this returns raw database permissions vs effective permissions.

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 efficient, but the '[UNIFIED]' prefix wastes space without adding value to the agent. Otherwise appropriately sized for the tool's complexity.

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?

Inadequate given zero schema documentation and lack of annotations. For a 2-parameter read operation with no output schema, should at minimum explain both parameters, especially 'site' which is ambiguous.

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 coverage is 0% with no descriptions for either 'site' or 'id'. While the description mentions 'by ID' (giving semantic context to one parameter), 'site' is completely unexplained despite being required and likely referring to a tenant/endpoint 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 clear verb (Get) and resource (permission details) with scope (by ID). However, the '[UNIFIED]' prefix is noise, and it doesn't distinguish from sibling directus_get_my_permissions (current user) vs fetching any permission by 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 versus directus_list_permissions or directus_get_my_permissions. No mention of prerequisites or access requirements.

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