appwrite_delete_user_sessions

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

No annotations provided, so description carries full burden. Explains behavioral effect well ('force logout everywhere') indicating immediate user impact. However, lacks safety disclosures common for destructive operations: no mention of irreversibility, required permissions, or side effects on active connections.

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 efficient sentence front-loaded with action verb. '[UNIFIED]' prefix is metadata noise but minimal. No redundant phrases or tautology.

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 zero schema descriptions, no annotations, and no output schema for a destructive operation, the description is insufficient. Should explain 'site' parameter semantics, User ID format expectations, and security prerequisites for global session deletion.

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. Description mentions 'for a user' which implicitly maps to user_id parameter, but provides zero explanation for 'site' parameter (unclear if URL, ID, or name). Insufficient compensation for undocumented schema.

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?

Description uses specific verb 'Delete' with resource 'sessions' and clarifies scope as 'all sessions' with parenthetical '(force logout everywhere)'. This clearly distinguishes it from sibling tool 'appwrite_delete_user_session' (singular) by explicitly stating the plural/all scope.

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?

Implies usage context with 'force logout everywhere', suggesting when to use it (global session termination). However, lacks explicit comparison to singular 'delete_user_session' sibling or prerequisites like admin privileges.

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