Browser HTTP Basic Auth

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the pre-navigate ordering constraint and the native-dialog nature of the credential, but is silent on persistence scope (does it apply only to the current page or all subsequent requests?), whether credentials survive navigation, and what happens on auth failure.

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?

Three tightly written sentences. The core identity (native auth dialog) is front-loaded, followed by the timing instruction and the cleanup note; no sentence is filler.

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 5-parameter, no-output-schema tool, the description covers identity, timing, and cleanup well, and the fully-described schema handles the parameter details. It falls just short of complete because credential persistence scope is never clarified, but an agent has enough to invoke it correctly.

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%, so the schema already documents mode, clear, username, password, and sessionId, including the 'required unless clear:true' constraint. The description reinforces clear:true but adds no syntax or format detail beyond the schema, making the baseline 3 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?

States a specific verb pair (set/clear) and resource (HTTP Basic/Digest Auth credentials), and crucially disambiguates from sibling tools by contrasting the native browser dialog against an on-page login form (browser_form_fill/browser_type). An agent can identify this tool without opening the schema.

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 instructs when to call it ('BEFORE browser_navigate to a protected URL'), gives a concrete scenario (password-protected staging site), and states the condition for the reverse operation (clear:true to remove credentials afterward). This is a full when/when-not/ordering guide.

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