ui_session_stop

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

No annotations are provided, so the description carries the full burden. 'Stop and dispose' indicates a destructive action, but it does not disclose side effects, idempotency, behavior with invalid session IDs, or impact on associated resources. This lacks transparency for a terminating 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 and target. Every word contributes meaning; there is no fluff or redundancy, making it an appropriately sized description.

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 stop operation, the description covers the basic purpose. However, it omits details such as return values, error behavior, prerequisites (e.g., session must be active), and whether the operation is idempotent. Given the low complexity and lack of output schema, this is minimally adequate but not complete.

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 one parameter, sessionId, with 0% description coverage. The description does not mention this parameter, add meaning beyond the name/type, or clarify whether it is required. The schema's optional flag is ambiguous, and the description fails to compensate for the zero coverage.

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 the specific verb 'Stop and dispose' and clearly names the resource 'Playwright UI session'. It distinguishes itself from sibling tools like ui_session_start and ui_navigate by indicating it ends a session.

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 usage—it is the counterpart to ui_session_start—but does not explicitly state when to use it or provide alternatives. No exclusions or conditions are mentioned, leaving usage to be inferred from context.

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