login_to_hudl

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

With no annotations, the description carries the full burden and does so well: it discloses the visible browser window, the target URL, the completion condition (navigation to /home), the state file location (~/.hudl_mcp/auth_state.json), automatic browser close, session update, and the guarantee that no password is stored. That is exactly the behavioral context an agent needs.

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 core action and the automatic-save mechanism are front-loaded in the first paragraph, with useful elaboration following. Slightly verbose in places, and the Returns section duplicates information already implied by the output schema, but nothing is wasted.

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 single-parameter interactive auth tool with no annotations, the description covers preconditions, the user's role in the flow, the completion trigger, side effects (state file, session update, browser close), and failure reporting. An agent can call and reason about this tool correctly without further information.

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 0%, so the description must compensate — and it does, defining timeout_seconds as the maximum wait for login completion and restating the 300s/5-minute default. It adds meaning beyond the bare schema but does not say what happens on timeout expiry (error vs. partial state).

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 first line states a specific action and resource: open an interactive pop-up browser to log into Hudl and save session state. It is clearly distinguishable from siblings like refresh_hudl_cookie (which implies reusing an existing session rather than a fresh interactive login).

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 clearly describes the context of use: interactive login via password manager, Google/Apple SSO, or 2FA, and explains the automatic completion trigger. It does not explicitly state when to prefer this over refresh_hudl_cookie, so the agent must infer that this is the first-time/expired-session path.

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