Log in to Glovo

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

No annotations are provided, so the description carries full burden. It discloses that Chrome is opened and a local session is saved, but lacks details on side effects (e.g., user interaction required, browser state modification, timeout behavior, or re-login implications).

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 a single, front-loaded sentence that efficiently conveys the action and purpose. No redundant or extraneous 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 the simple input schema (one optional integer) and no output schema, the description adequately explains the tool's role for subsequent tools. However, it could be enhanced by noting that it requires a browser environment and may involve manual login steps.

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%, with a clear description for the single parameter (timeout_ms). The tool description adds no parameter information, but baseline is 3 when schema coverage is high. Thus score is adequate.

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 ('Open Chrome for Glovo sign-in') and the purpose ('save the local session for order history and basket tools'). It distinguishes the tool from siblings by indicating it is a prerequisite for other tools like basket and history.

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 implies usage as the first step for other tools by mentioning 'save the local session for order history and basket tools.' However, it does not explicitly state when not to use it or offer alternatives, though sibling names like glovo_auth_status suggest a complementary tool.

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