browser.save_auth_profile

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

The description omits details beyond 'save', such as whether an existing profile with the same name is overwritten, any prerequisites (e.g., session must have a certain state), or what the return value is. Annotations provide basic read/write hints but add no depth.

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, well-formed sentence that immediately conveys the purpose. There is no redundant or extraneous information.

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 simple tool with two required parameters and no output schema, the description is minimally adequate. However, it lacks details about the effect on the session, any side effects, or the return format, which an agent would need for correct invocation.

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?

With 0% schema description coverage, the description should clarify parameters. It mentions 'session_id' and 'profile_name' by name but does not explain that session_id refers to an existing browser session or how profile_name is used for reuse.

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 verb 'Save' and the resource 'current session storage state into a reusable named auth profile.' It distinguishes this tool from siblings like 'get_auth_profile' and 'list_auth_profiles' by focusing on saving state.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'save_memory_profile' or 'get_auth_profile'). The description does not clarify that this is intended for persisting authentication state after login.

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