session_logoff

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

Goes well beyond the destructiveHint annotation by explaining the profile write-back side effect, the preview default (confirm=False), the audit trail, and the substring match with refusal if no matches. This is valuable behavioral context not available from annotations alone.

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?

Well-structured with a clear [WRITE] tag, effect summary, usage explanation, and bulleted args list. Every sentence adds necessary detail without redundancy, and the most critical information (destructive action, preview-first) is front-loaded.

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?

Covers all essential aspects: target selection, safety preview, side effects, auth implications (audited), and config behavior. Despite no output schema, it describes exactly what the preview returns (blast radius, session count, affected users). The description is self-sufficient for correct 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%, but the Args section fully documents all four parameters with their semantics: session_ids for explicit IDs, user for AD substring, confirm for preview/apply, and target for config override. This fully compensates for the bare 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?

The description immediately states a specific verb and resource: 'Force-logoff Horizon session(s)' with concrete effects ('kicks the user, triggers profile write-back'). It clearly distinguishes from sibling tools like session_disconnect and session_send_message.

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 clear usage context: how to target sessions (session_ids or user), the preview/confirm workflow, and refusal behavior when no user matches. Does not explicitly name alternative tools or state when not to use it, but the targeted guidance is strong.

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