scout_session

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

With no annotations provided, the description carries full behavioral burden. It discloses that both browsers remain live and authenticated regardless of default choice, and that re-snapshotting after a break reveals changes. This adds meaningful state-lifecycle context beyond the basic action.

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?

Three sentences, front-loaded with the core action, and every sentence earns its place: the first states purpose, the second gives usage guidance, the third clarifies persistent browser state. No filler or repetition of schema content.

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 only two simple parameters, no annotations, and no output schema, the description covers purpose, default behavior, concurrency trade-offs, and persistence of browser sessions. It does not spell out return format or conflict behavior if both `name` and `session` are supplied, but these are minor for this tool's simplicity.

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%, so baseline is 3. The description adds extra meaning by explaining the default selection applies to any tool call that omits `session`, and why that matters for concurrent dispatch. This goes beyond the schema's parameter descriptions.

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 specific verb and resource: 'List live sessions, or set which one is the DEFAULT.' It clearly distinguishes this tool from the broader scout_* family by centering on session default management and live-session listing, so an agent can tell what it does without opening schemas.

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 direction: prefer passing `session` directly for multi-role/concurrent work, and use scout_session for sequential convenience and checking live sessions. This is exactly the when-to-use versus when-not-to-use guidance needed.

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