stop_session

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

Without annotations, the description discloses core behavioral traits: it closes connections and terminates the app process. It also states idempotency via 'Safe to call twice.' Missing details on side effects to other sessions or error handling, but overall transparent.

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 sentences with no filler. The first sentence captures purpose and actions; the second provides a safety note. Structure is front-loaded and efficient.

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 one parameter and no output schema, the description covers the main action and idempotency. It doesn't mention return value or error states, but it is largely complete given the context.

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 100% with the parameter 'sessionId' described as returned by launch_app. The description does not add further meaning, so baseline score of 3 is appropriate.

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 the action ('stop a debug session') and specifics ('close CDP connections and terminate the app process'). It distinguishes from sibling tools like launch_app and pause by being the definitive session-ending operation.

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 (when ending a debug session) and notes safety of calling twice, but lacks explicit instructions on when not to use or alternatives. No comparison to siblings like pause or resume.

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