Start Session

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

The annotations already indicate this is a non-read-only, non-destructive, idempotent operation. The description adds the nuance of 'resume,' implying it works on existing sessions, but does not disclose what happens if the session_id is invalid, whether a new session is created if none exists, or what the response contains. Minimal added value beyond 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, concise sentence that front-loads the action and includes a useful parenthetical clarification ('or resume'). No wasted words, appropriately sized for a simple tool with one parameter.

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 with one parameter and has annotations covering safety, but the description leaves key context gaps: whether the session must already exist, how this relates to session creation, and what the return value is. Given the large number of sibling session tools, more clarity on when to use this tool would improve 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 has 100% coverage, fully describing session_id as 'The session id to start.' The description adds no additional parameter meaning beyond this. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 tool's function: 'Start (or resume) an inference session.' It uses a specific verb and resource. However, it does not explicitly distinguish this from the many sibling session tools (e.g., lyzr_session_create), leaving slight ambiguity about whether 'start' implies creating a new session or activating an existing one.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention that this is for resuming an existing session or when to prefer lyzr_session_create, lyzr_session_get, or lyzr_chat. The user must infer usage from the name alone.

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