Create Session (v3)

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

Annotations already indicate a write operation (readOnlyHint false) and openWorldHint true, but the description adds no additional behavioral context. It does not mention side effects, persistence, response behavior, or any requirements beyond the schema, and does not clarify the implications of openWorldHint.

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, front-loaded sentence with no redundant wording. It communicates the essential purpose efficiently, earning a 5 for conciseness.

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?

Given the absence of an output schema and the presence of openWorldHint true, the description should clarify what the tool returns or what side effects occur, but it does not. It also fails to guide an agent in choosing among the many session-related sibling tools, leaving important gaps.

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 descriptions cover 100% of parameters, including the optionality of agent_id. The description's phrase 'optionally tied to an agent' merely reiterates schema information without adding new meaning, so the baseline 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 uses a specific verb ('Create') and identifies the resource ('a new v3 session'), clearly distinguishing it from the sibling tool lyzr_session_create_by_agent by noting the optional agent association. The 'v3' designation also separates it from lyzr_session_create.

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 implies usage for creating v3 sessions, optionally tied to an agent, but does not explicitly state when to choose this over lyzr_session_create or lyzr_session_create_for_agent. No exclusions or alternative recommendations are provided.

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