carrefour_browser_login

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

Beyond the apparent side effects (a browser is displayed), the description provides important stateful behavior: the SSO cookie that can renew itself is retained in the server profile. Also captures the login anti-automation behavior (Turnstile won't validate). No annotation variables to fill side effects.

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?

Five sentences describe the entire procedure, constraints and persistence. No filler, no redundancy, and every sentence adds new 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 zero-param tool with no output schema, the description sufficiently covers the important user-relevant context: the profile session stays in the profile, the login cannot be automated. It is not overly complex; no output structure needed.

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 input schema is an empty object, no parameters; the schema already captures all required details. Baseline of 4 applies due to high schema coverage and no parameters requiring additional elaboration.

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?

Description uses a specific verb+resource ('Opens a browser window on the server profile so you can sign in to carrefour.fr') and names the exact target site. It also describes the complete login workflow (captcha, emailed OTP, close window, session keeps). This distinguishes it from siblings like carrefour_session_status or get_cart.

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?

Description clearly states the context: manual login needed on carrefour.fr. It says that automation cannot be performed: Turnstile refuses to validate in a controlled browser. It does not explicitly name alternative tools, but conveys the appropriate scenario.

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