Stop Session

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

Beyond the structured annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description adds no additional behavioral context. It does not disclose what happens to the session after stopping, whether it can be restarted, whether resources are released, or what the return value is. The 'active' qualifier is a mild pointer but not explicit about behavior for already-stopped sessions.

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 sentence, 'Stop an active inference session.', which is concise, front-loaded with the action, and contains zero wasted words. This is 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?

For a simple one-parameter mutation tool with no output schema, the description is minimally sufficient but lacks details about return values, post-stop state, or any side effects. Given the subject matter complexity and the presence of annotations, a score of 3 is appropriate, as there is a slight gap in fully characterizing the tool's behavior.

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 input schema fully describes the sole parameter session_id as 'The session id to stop', providing 100% schema description coverage. The tool description adds no additional parameter semantics, such as format, example, or further explanation, so the baseline 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 'Stop' and the target 'active inference session', which is a specific resource. It distinguishes from sibling tools like lyzr_session_delete by the 'active' qualifier and the verb 'Stop', indicating termination of an ongoing process rather than deletion of 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?

The description provides no explicit guidance on when to use this tool versus alternatives such as lyzr_session_delete, lyzr_session_update, or lyzr_start_session. There are no prerequisites, no exclusions, and no mention of when not to use it. The only implied context is that it applies to 'active inference sessions'.

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