dbg_terminate

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

No annotations are provided. The description indicates destructive behavior ('kill' or 'detach') and mentions freeing a session, but does not elaborate on what resources are freed, whether the operation is reversible, or what happens to associated state. Without annotations, the description should provide more behavioral context.

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 at one sentence, but the parenthetical clauses create confusion rather than clarity. Front-loading is acceptable, but the structure could be improved by separating the two modes or providing clearer phrasing.

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?

Given the tool has one required parameter and no output schema, the description lacks information about return values, error conditions, or side effects. The phrase 'free the session' is vague. The description is insufficient for an agent to use the tool confidently.

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 parameter (session_id) with no description, and the schema description coverage is 0%. The tool description does not explain the parameter's meaning, format, or constraints, leaving the agent without essential usage information.

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 it kills/detaches and frees the session, providing a specific verb and resource. However, the parenthetical '(launch)' and '(attach)' introduce ambiguity about what exactly is being killed or detached, making the purpose less clear than it could be.

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 on when to use this tool versus alternatives like dbg_pause or dbg_continue. The description does not specify prerequisites, such as whether the session must be running or attached, nor does it mention when not to use it.

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