Get Session

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds no extra behavioral context (e.g., not-found behavior, timeout semantics, return format) beyond the basic fetch operation, which is consistent with annotations.

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, short sentence that is immediately understandable. No filler or redundancy; every word is necessary. It is appropriately sized for a simple get operation.

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 simple get-by-id tool with strong annotations and fully described parameters, the description is mostly complete. However, it does not explicitly mention what a 'session' refers to in this context (e.g., legacy vs. session3) or describe the return value, but the output schema is absent, so the agent must infer the response shape from the operation name.

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%, with both session_id and timeout having descriptions in the schema. The description itself adds no parameter-level meaning, so it relies on the schema to convey semantics. This matches the baseline for good schema coverage.

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 session by id' clearly states the verb (fetch), resource (session), and scope (by id). It does not explicitly differentiate from sibling tools like lyzr_session3_get or lyzr_session_history, but the name and 'by id' make the intended operation clear.

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 provides no guidance on when to use this tool versus alternatives such as lyzr_session_history or lyzr_session3_get. There is no mention of when to use or when not to use, leaving the agent to infer usage purely from the name.

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