kill_session

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

With no annotations, the description carries the full behavioral burden. It discloses that gdb sessions are detached by default and only terminated with force=True, and that script sessions are gracefully ended or killed with force=True. This goes well beyond the name, though it omits other side effects like idempotency or resource cleanup.

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?

Two concise sentences front-load the core action ('End a session') and then immediately provide the key behavioral distinctions. Every sentence earns its place with no filler or repetition of schema data.

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 covers the main behavioral variations and force semantics, but it omits the meaning of session_id and any mention of return values or error cases. For a tool with two simple parameters and no output schema, it is reasonably complete but has clear gaps around parameter usage and expected results.

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 0% description coverage, so the description must compensate. It explains the force parameter's effect for gdb and script sessions, but it does not clarify the session_id parameter—whether null means the current/latest session or something else. This leaves one of two parameters underdocumented.

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 states a clear verb and resource ('End a session') and adds valuable differentiation between gdb and script sessions, including the default versus force behaviors. It doesn't explicitly name sibling alternatives like quit_gdb, but the behavior described makes the tool's purpose distinct.

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 explains how force affects gdb and script sessions but does not say when to prefer kill_session over quit_gdb or other session-related tools. There is no explicit when-to-use or when-not-to-use guidance, leaving the agent to infer selection criteria.

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