mobbin_connect

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

With no annotations, the description carries the behavioral burden. It discloses that saved sessions are restored, that headless mode affects visibility, and that this tool does not handle authentication (mobbin_login is needed). This is valuable context beyond the schema, though it doesn't detail outcomes or failure modes.

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 sentences, front-loaded with the primary purpose. Each sentence adds distinct value: operation, session behavior, and usage guidance. 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?

Given the simplicity of the tool (one optional boolean param, no output schema), the description covers the essential aspects: launch, session restore, headless usage, and the next step if unauthenticated. It could mention expected outcome or failure, but it is largely complete for an entry-point tool.

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 description coverage is 100% for the single 'headless' parameter, already stating 'Set false for interactive login'. The description adds 'so you can see the browser window' and ties it to first-time login, but this is a rationale, not new semantic meaning. Baseline 3 is appropriate.

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 'Launch a browser and connect to Mobbin', using a specific verb and resource. It distinguishes itself from sibling mobbin_login by indicating that authentication is handled separately after connection, making the tool's unique role obvious.

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 explicit guidance: use headless=false for first-time login, and after connecting, use mobbin_login if not authenticated. This clarifies when to use this tool versus the login alternative and sequences the workflow.

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