browser.save_auth_profile

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

The description states what is captured (current session storage state) and where it is stored (a reusable named auth profile), which is the core behavioral contract. However, it does not disclose overwrite behavior, whether an authenticated session is required, or what the tool returns; the annotations are all false flags and do not fill that gap.

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?

One sentence with no filler; it front-loads the action and destination. Every word contributes to the meaning.

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 two-parameter save action, the required inputs are clear and the schema covers them well. However, there is no output schema and the description does not mention what happens on success, what the call returns, or what occurs when an existing profile name is reused, leaving moderate 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?

Schema description coverage is 100%, and the schema already documents both parameters clearly, including the optionality of session_id and the relationship of profile_name to browser.create_session. The description adds no parameter-level detail beyond the schema, so baseline 3 applies.

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 names a specific action and resource: save the current session storage state into a named auth profile. This clearly differentiates it from siblings like list_auth_profiles, create_session, and close_session.

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 implies the use case by calling the profile 'reusable,' and the schema explains that the resulting profile is passed to browser.create_session, but the description itself gives no explicit when-to-use guidance or exclusions. An agent can infer the intended workflow but is not told directly when to prefer this over alternatives.

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