login_shufersal

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

With no annotations, the description carries the full burden and discloses key behaviors: it opens a browser window, requires the user to complete sign-in manually on the site, and captures the session automatically. The Playwright installation prerequisite is also valuable operational context. It does not cover edge cases like existing sessions or error handling, but it is solid for a login flow.

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 three short sentences, front-loaded with the main action and followed by the automatic capture behavior and the prerequisite. Every sentence earns its place with no wasted words.

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?

The description explains the login flow, the automatic session capture, and the environment prerequisite. Because an output schema exists, return values need not be described. The main missing contextual link is how this tool relates to sibling tools like login_status and check_login after the session is captured.

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 tool takes zero parameters, so there are no parameter semantics to document. The baseline for a zero-parameter tool is 4, and the description appropriately does not invent parameter details.

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: 'Open a browser window for Shufersal login' and 'Complete the sign-in on shufersal.co.il.' This distinguishes it from most siblings by naming Shufersal, but it does not explicitly contrast with the sibling login_tivtaam, so sibling differentiation is only implicit.

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?

Usage is implied: the tool is for logging into Shufersal, and a prerequisite is given ('Requires Playwright: run `uv run playwright install chromium` once'). However, there is no explicit guidance on when to choose this over alternatives like login_tivtaam, login_status, or check_login.

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