scout_close

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

No annotations are provided, so the description carries the full burden of exposing side effects. It directly discloses that memory persists on disk after closing, and that all=true only affects live sessions. This goes well beyond the schema's parameter descriptions and helps the agent predict the tool's impact.

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 one compact sentence that front-loads the core function and persistence caveat, then covers all invocation modes without redundancy. Every clause contributes useful information.

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 two optional parameters, no output schema, and no annotations, the description is complete: it states what is closed, the persistence behavior, the default behavior, how to target one session, and how to close all sessions. Nothing material is missing for correct selection and invocation.

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 already covers both parameters with 100% description coverage, so the baseline is 3. The description adds useful semantic context: session targets one browser, all=true is intended for multi-role run cleanup, and omitting both closes the DEFAULT session. This extra guidance justifies a slightly higher score.

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 names a specific verb and resource ('Close a session's browser') and clearly distinguishes this teardown action from the other scout_* tools, which are about scanning, navigating, clicking, or reporting. It also communicates the key scope variants (default session, specific session, all sessions).

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 gives explicit usage conditions: no session argument closes the DEFAULT session, session closes a named session, and all=true closes every live session at the end of a multi-role run. It does not explicitly mention when not to use this tool or name an alternative, but no sibling tool performs closing, so the guidance is sufficient.

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