Log In Via Headless Browser (all services)

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

With no annotations, the description carries full burden. It discloses browser use, password security, best-effort per-service behavior, and session reuse. It does not mention rate limits, but overall provides substantial behavioral context.

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 front-loaded with the core action and each sentence adds value. It covers purpose, usage, behavior, and limitations without redundancy.

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 simple input schema (one optional boolean), no output schema, and complex task, the description thoroughly explains the tool's role, how it works, and its relationship to sibling tools, leaving no major gaps.

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 single parameter 'force_relogin' is explained in the description: 'Mints once and reuses the session on later calls unless force_relogin is set.' This adds critical meaning beyond the schema, compensating for 0% schema coverage.

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 tool drives a headless browser for ADFS SSO login using email+password, completes multiple SAML handshakes, and returns an opaque session_id for use with other tools. It distinguishes from sibling tools like *_bootstrap_session for MFA accounts.

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 explicitly says 'Only works for accounts without interactive MFA (use the *_bootstrap_session tools for MFA accounts)' and notes the session is reused unless force_relogin is set, providing clear guidance on when and when not to use this tool.

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