List Agent Sessions

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

The description adds no behavioral traits beyond what the annotations already provide (readOnlyHint, openWorldHint, idempotentHint). It does not mention pagination, sorting, return format, or any session-specific caveats, so it fails to add value beyond the structured hints.

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 concise sentence that clearly states the action and target. It is appropriately sized, though slightly under-specified regarding selection context, which prevents a perfect score.

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 tool is simple with one parameter and strong annotations. The description is enough to invoke it correctly, but the lack of guidance on which session type or alternatives to use is a minor gap, given the many sibling tools.

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 single parameter agent_id is fully covered by the schema with a description ('Agent id'), and the description's 'for an agent' adds minimal extra context. This meets the baseline for good schema coverage; no further semantics are needed.

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 uses a specific verb (List) and resource (sessions for an agent), making its purpose clear. However, it does not distinguish among the many sibling session listing tools such as lyzr_session3_list or lyzr_session_history_by_agent, so it misses the differentiation needed for a 5.

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?

There is no guidance on when to use this tool versus alternatives. With numerous session-related sibling tools, the description should specify exclusions or conditions, but it provides none.

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