Set session goal (Jev pruning context)

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

With no annotations, the description carries the full burden. It discloses the behavioral effect on browser_snapshot (collapsing irrelevant regions) and the replace semantics on repeated calls. A minor gap is that it does not specify behavior when Jev is inactive, but this is not critical for a simple setter tool.

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 two sentences, front-loads the primary action, and includes only essential details. No fluff or redundancy; every sentence adds value.

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 single-parameter tool with no output schema, the description covers purpose, usage context, behavioral effects, and reusability. An agent can confidently call it correctly without additional information.

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% and the schema already defines 'goal' as 'What this browser session is trying to accomplish.' The description adds context that the goal is used for pruning, but that is more about tool behavior than parameter meaning. It does not add syntax or formatting details, so baseline 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 ('Set the session goal') with a specific resource and outcome. It distinguishes itself from siblings by explaining its unique role in Jev annotation pruning, and notes that calling again replaces the goal, which is unambiguous.

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 context for when to use it (when Jev annotation is active) and implies its benefit (saving context tokens). It does not explicitly name alternatives or state when not to use it, but the context is sufficient for an agent to understand its niche among the sibling tools.

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