iva_user_session

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

With no annotations, the description carries the disclosure burden; it adds a useful security note that login and 2FA actions are excluded and authentication is automatic. It does not disclose side effects such as logout ending the session or set_session_state mutating presence, although those details appear in the schema's action enum.

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 short and front-loaded with the key operation list. The security note is relevant and concise, and there is little wasted text apart from the minor 'Clients API v2.28.12' fragment.

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?

The schema's action enum provides detailed descriptions of each operation, including effects and examples, and all four parameters are documented. Description plus schema together give an agent enough context to invoke the tool correctly, though there is no output schema or return-format note for session info.

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 description coverage is 100%, so the baseline is 3. The tool description does not add parameter-level detail beyond naming operation areas; the schema already documents action, confirm, providerId, and sessionState.

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 opens with 'IVA user session management' and lists the concrete operation areas: logout, session info, guest login, session state, and login URL. This makes the tool's scope clear, though it lacks a single imperative verb and does not explicitly contrast with sibling tools.

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?

The description implies this tool is for session-related actions and explicitly excludes login/2FA, explaining that authentication is handled automatically via IVA_LOGIN/IVA_PASSWORD environment variables. However, it does not state when to prefer this tool over sibling tools or provide condition-based usage guidance beyond the authentication exclusion.

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