Get Session (v3)

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

Annotations already provide readOnlyHint and idempotentHint, but the description adds no behavioral context beyond restating the resource. It does not disclose what fields are returned, whether messages are included, or any error behavior, leaving the agent without additional safety or expectation-setting.

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, brief sentence with no filler or redundant phrases. All words are purposeful and the structure places the essence ('fetch v3 session') at the front.

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?

This is a simple getter with one parameter and favorable annotations, but no output schema exists. The description does not explain what the returned session contains or whether it differs from other session variants, leaving moderate ambiguity about the actual return payload.

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 100% and the single parameter session_id is clearly described in the schema as 'Session id to fetch'. The description adds no new parameter-level meaning beyond what the schema already states, so the baseline of 3 applies.

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 'Fetch a v3 session by id' uses a specific verb (fetch), names the resource (v3 session), and specifies the lookup method (by id). This clearly distinguishes it from sibling tools like lyzr_session_get and lyzr_session3_list.

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 implicitly signals use when you have a v3 session id and need the session object. However, it provides no explicit guidance on when to prefer this over lyzr_session_get or how to obtain the id via lyzr_session3_list, and it gives no exclusion criteria.

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