mobbin_login

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

With no annotations provided, the description carries full disclosure. It transparently explains the tool's non-deterministic behavior (manual user authentication), the 5-minute wait, the requirement for non-headless mode, and the side effect of saving session cookies. This gives significant insight beyond simple 'login' terminology.

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 extremely concise yet comprehensive, packing the main action, key prerequisite, timeout, and outcome into two sentences. Every piece of information is necessary, and the structure flows logically from action to prerequisite to result.

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 tool with no parameters, no annotations, and no output schema, the description covers the essential context: what it does, the manual step, the timeout, and the side effect. It doesn't specify what happens on timeout or the return value, but for this simple login tool with no output schema, the description is sufficiently complete.

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 accepts no parameters, so under the rubric the baseline is 4. The description does not introduce any implicit parameters and the schema is empty, so there is nothing more to explain. The description appropriately focuses on the process rather than parameter semantics.

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 identifies the tool's purpose: navigating to the Mobbin login page, waiting for manual authentication, and saving session cookies. It uses a specific verb+resource structure and distinguishes itself from sibling tools by focusing on the login workflow rather than general navigation or extraction.

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 provides clear context for when to use the tool, including the critical prerequisite that the browser must be launched in non-headless mode via mobbin_connect with headless=false. While it doesn't explicitly contrast with alternatives, it gives enough guidance on the required setup, making it clearly usable.

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