store_browser_session

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that forms run in a headless profile that does not seize the user's screen, that Apple sessions expire frequently producing meaningless reads, that relogin opens a visible window, and that 2FA cannot be automated so a human must intervene.

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 core statement is front-loaded on the first line and the following lines explain why it matters and how parameters change behavior. Slightly prose-heavy, but every sentence adds diagnostic context rather than filler.

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?

An output schema exists, so return values need not be described. The description covers purpose, trigger condition, and both parameters, leaving only small ambiguities such as whether relogin blocks until authentication completes.

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 0%, so the description must compensate, and it does: relogin=True is explained as opening an interactive window, and console is documented with its accepted values ('play' or 'apple') to scope the relogin. Minor gaps remain (e.g. the default relogin=False check-only behavior is only implied).

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 concrete resource and behavior: it reports the login state of the dedicated headless-Chrome console session, and with relogin=True it opens an interactive window. That is a specific verb-plus-resource, though it never explicitly distinguishes itself from similarly-named siblings such as store_doctor.

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?

It gives a clear trigger condition: check here before investigating a form that 'did not save', and explains when to use relogin=True or the console argument. It stops short of naming any alternative tool for diagnosing store problems, so it falls short of a full 5.

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