appwrite_delete_user_session

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. While 'Delete' implies destruction, it lacks details on immediate effects (user logout), reversibility, or required permissions beyond the parameter schema.

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 and front-loaded, but the '[UNIFIED]' prefix appears to be metadata noise rather than descriptive content. Given the complete lack of schema documentation, the single sentence is excessively terse rather than appropriately concise.

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, no output schema, and ambiguous sibling relationships, the description provides inadequate context. Critical gaps remain around parameter semantics and behavioral side effects necessary for safe 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?

Schema coverage is 0% with three undocumented parameters (site, user_id, session_id). The phrase 'specific user session' implies the purpose of session_id but fails to explain 'site' (an Appwrite project/endpoint identifier) or confirm that user_id identifies the session owner. Insufficient compensation for complete schema lack.

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 provides a clear verb (Delete) and resource (user session), and uses 'specific' to imply singular targeting. However, it fails to explicitly distinguish from the sibling tool 'appwrite_delete_user_sessions' (plural), which deletes all sessions rather than one.

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 provided on when to use this singular deletion versus the plural 'delete_user_sessions' alternative. No prerequisites mentioned (e.g., that session_id typically comes from list_user_sessions).

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