territory_login_browser

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

Since no annotations are provided, the description carries full responsibility for behavioral disclosure. It mentions a 'visible browser window' (user interaction required), 'one-time' authentication, and that it captures and saves a session cookie. It does not specify what happens on failure or whether it overwrites an existing session, but the core behavior is well disclosed.

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 succinct sentence that conveys the key points without fluff. It covers the action, the target, the mechanism, and the outcome in a compact form.

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 an authentication tool with no annotationslogging, the description provides good context: it tells the agent that user interaction is required (visible browser), it captures a session cookie, and it has a timeout. It lacks information about return values or failure modes, but these may be less critical for a this kind of tool. Overall, it is fairly 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 only parameter, timeoutSeconds, is fully described in the schema with its default value (180s). The description reinforces its purpose by saying 'Max seconds to wait for user to sign in.' There is no ambiguity.

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 ('Launches a visible browser window'), the specific resource ('Territory News'), and the outcome ('Captures the session cookie and saves it locally'). It is distinct from sibling tools like territory_auth_status (checking status) and territory_logout (ending session), making the purpose unambiguous.

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?

It describes the tool as 'one-time authentication' which gives context, but it does not explicitly state when to use this versus alternatives, nor does it mention prerequisites like needing to check auth status first. The guidance is implicit rather than explicit.

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