avanza_sessions

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

With no annotations provided, the description carries the behavioral disclosure burden. It does indicate the operation is a read-only listing and adds the 'currently loaded in TUI' qualifier, which clarifies the source of data. However, it does not disclose what a session represents, whether any precondition exists, or what the returned session objects contain.

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 a single, compact sentence that is front-loaded with the action and resource. Every word contributes value, and there is no redundant or vague filler.

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?

For a zero-parameter, read-only listing tool, this description is nearly complete. It names the exact scope of the listing and implies the return is a list of sessions. It could add slightly more context about what constitutes a 'session' or how this relates to selecting one, but the minimal surface area makes this a minor gap.

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?

The tool has zero parameters and the schema is an empty object, so the baseline is 4. There are no input semantics the description needs to explain, and adding parameter detail would be irrelevant.

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 identifies a specific verb ('List') and resource ('authenticated Avanza tenant sessions currently loaded in TUI'), making the tool's purpose immediately understandable. It conveys that this is a read-only enumeration of locally loaded sessions rather than an authorization or selection action, though it 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 gives no guidance on when to use this tool versus alternatives such as avanza_select_session, avanza_live_session_authorize, or avanza_live_session_revoke. It only states what it lists, leaving the agent to infer that it is likely useful for inspecting currently active sessions before selecting one.

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