appwrite_list_user_sessions

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

No annotations provided, so description carries full burden. 'List' implies read-only and 'active' suggests filtering, but description omits auth requirements, pagination behavior, session data format, and whether this operation is logged or rate-limited.

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 concise and front-loaded with the action verb. However, the '[UNIFIED]' prefix appears to be metadata noise that doesn't add semantic 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?

Inadequate for a tool with zero schema documentation and no annotations. Missing critical context: output structure, parameter semantics for 'site', and differentiation from related session management tools.

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 parameter descriptions. While description mentions 'for a user' implying user_id, it completely fails to explain the 'site' parameter (format, valid values, relationship to Appwrite projects).

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 (List) and resource (active sessions for a user) clearly. However, it does not explicitly distinguish from sibling deletion tools like `appwrite_delete_user_sessions` or clarify if this includes all sessions across devices.

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 `appwrite_get_user` or deletion siblings, no prerequisites mentioned, and no indication of required permissions (e.g., admin vs self-service).

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