sassy_session_stop

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

No annotations are provided, so the description carries full responsibility. It mentions 'clean up' which hints at side effects beyond stopping, but does not disclose what cleanup entails, whether the action is reversible, or what happens to running processes. This is a significant gap for a destructive operation.

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 is front-loaded with the action. It contains no filler or redundant phrases, earning high marks for efficiency, though it could be slightly more informative without losing 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?

For a tool with no annotations and minimal description, the context is incomplete. The agent lacks information about the session ownership, cleanup side effects, or how to recover if the wrong session is stopped. The presence of an output schema does not mitigate the need for behavioral context in a state-changing tool.

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 has one required parameter 'name' with 0% schema description coverage. The description does not explain what 'name' refers to, how to find valid session names, or any format constraints. While the purpose implies it is the session identifier, the description fails to compensate for the missing schema documentation.

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 ('Stop') and resource ('terminal session'), clearly indicating the action. While it does not explicitly distinguish from sibling 'sassy_session_stop_all', the tool name and singular phrasing imply it stops one session, which is a reasonable differentiator.

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 provided on when to use this tool versus alternatives like 'sassy_session_stop_all' or 'sassy_session_list'. There is no mention of prerequisites (e.g., an active session) or exclusions, leaving the agent to 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.