sassy_session_start

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

The description discloses key behavioral traits: sessions are persistent, shell selection varies by OS, and the command is optional. However, it does not mention side effects such as creating a background process, the need for cleanup, or how the session is identified later. Given no annotations, this is adequate but not rich.

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 concise, front-loaded with the main purpose, and follows a clean parameter list format. Every sentence adds value without redundancy.

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 description is complete for starting a session, covering all parameters and the persistent nature. It would benefit from mentioning related session tools (e.g., sassy_session_send) for lifecycle context, but the existing content is sufficient for the tool's direct purpose.

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 coverage is 0%, so the description fully compensates by explaining each parameter: name's purpose with examples, shell's platform-specific values and default behavior, and command's optional initial instruction. This adds vital meaning beyond the empty schema descriptions.

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 'Start a persistent terminal session' with a specific verb and resource. It distinguishes itself from siblings like sassy_session_send, sassy_session_read, and sassy_session_stop by focusing on the start action.

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 when to use the tool (when starting a persistent terminal session) but does not explicitly reference alternatives or mention when not to use it. The shell parameter guidance provides some usage context but not tool-selection guidance.

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