login

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

With no annotations, the description carries full behavioral burden and does so well: it discloses browser opening, the short-lived 127.0.0.1 listener, the config file location, and that it returns immediately with a URL. This gives the agent a realistic model of the 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?

The description is compact yet information-dense, starting with the main purpose and ending with side effects. Every sentence contributes: purpose, flow, return behavior, when to use, and side effects.

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-parameter login tool with no output schema, this is complete: the agent knows what triggers login, what happens in the browser, what is returned, where credentials are stored, and how to retry the originating tool. No critical operational detail is missing.

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?

There are zero parameters and the schema is empty, so the baseline is 4. The description adds useful context by explaining the browser interaction and access-choice flow, which is more than the schema alone could convey.

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?

States a specific action ('Log in to Mockzilla cloud') and the concrete effect: hosted tools become available. It also distinguishes itself from local tools and from logout by naming the hosted-tool context.

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?

Explicitly says when to call it ('when a hosted tool says it needs a login') and what to do next ('call that tool again once the user approves'). It also says local tools never need it, giving a clear exclusion.

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