Get Session Conversation

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, establishing the safe read-only nature of the operation. The description adds no additional behavioral details such as error handling or return format, but it does not contradict the annotations either. With the lower bar set by annotations, this is adequate but minimal.

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 front-loads the primary purpose without any filler. It is appropriately sized for a simple read tool, though it could have included contextual alternatives without becoming verbose.

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?

While the tool is simple with one parameter and no output schema, the description fails to provide enough context to distinguish it from numerous sibling session tools. It neither clarifies the return format nor explains the difference between session, session3, and history tools, leaving the agent without full situational awareness.

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 schema provides 100% coverage for the single parameter session_id with a clear description ('Session id'). The tool description does not add further parameter semantics, but given the high schema coverage, the parameter is well-documented and the baseline score of 3 is appropriate.

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 clearly states the action ('Fetch') and the resource ('a session's conversation'), making the tool's purpose immediately apparent. However, it does not differentiate it from sibling tools like lyzr_session_get or lyzr_session_history, which could also be interpreted as fetching session data.

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 over alternatives. Given the extensive list of session-related sibling tools (lyzr_session_get, lyzr_session_history, lyzr_session_summary, etc.), the absence of usage context is a notable gap that could lead to incorrect tool selection.

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