Create Isolated Eden Session

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

The description adds meaningful behavioral context beyond the destructiveHint annotation by specifying the session is 'idle' and has a 'cloned portable profile and independent executable'. This helps the agent understand the nature of the action and its side effects, without contradicting the annotation.

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 two concise sentences with no filler. The first sentence defines the action and key attributes; the second explains how to use the result. Every word contributes to understanding.

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 tool with an output schema, the description covers the core purpose and the workflow well. However, the optional input parameter is left unexplained, and the destructive hint is not elaborated on, which leaves some gaps for an agent deciding how to invoke the tool correctly.

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 one optional parameter (session_id) with 0% coverage in the description. The description only mentions session_id as a return value ('Pass the returned session_id'), leaving the meaning of the input parameter completely unexplained—whether it is used to clone from an existing session, reference a parent, or something else.

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 the specific verb 'Create' and clearly identifies the resource (Eden session) with valuable qualifiers: 'idle', 'cloned portable profile', and 'independent executable'. This distinguishes it from sibling tools like eden_list_sessions and eden_stop_session, which manage or list existing sessions rather than create new ones.

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 instruction to 'Pass the returned session_id to all normal control tools' provides clear workflow context: this is the entry point for using other control tools. It implies the tool should be used before session control tools, though it does not explicitly state when not to use it or mention alternatives.

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