Get Session Summary

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

Annotations declare readOnlyHint=true and idempotentHint=true, so the agent already knows this is a safe read operation. The description adds no further behavioral traits beyond the action itself, such as what the summary contains or any dependencies. It is consistent with annotations, so no contradiction. With annotations covering the safety profile, this is adequate but adds minimal context.

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, clear sentence with no unnecessary words. It is front-loaded and immediately conveys the action and target. This is appropriately concise for such a simple read 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?

The tool is simple (1 parameter, no output schema), but the description lacks clarity on what a 'session summary' actually contains or how it differs from other session tools. Without an output schema, the agent is left unaware of the return value's structure or content. This is adequate for a trivial fetch, but the ambiguity among many sibling tools reduces completeness.

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, described as 'Session id'. The description repeats the concept of a session but doesn't add meaning beyond the schema. Per the baseline rule for high schema coverage, a 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 uses a specific verb and resource: 'Fetch a session's summary.' This clearly states what the tool does. However, it doesn't explicitly distinguish it from sibling tools like lyzr_session_conversation or lyzr_session_history, which are also session-related retrievals. The name and title help, but the description alone doesn't disambiguate.

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. The description only states the action without indicating context, prerequisites, or when a different session tool would be more appropriate. Given the large number of session-related sibling tools, this is a significant omission.

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