browser.save_memory_profile

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

The description adds that profiles are loaded later, but does not disclose overwrite behavior, authentication needs, or other side effects. Annotations are minimal, so description carries some burden but falls short of fully transparent.

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 two concise sentences, front-loaded with the action, and no unnecessary words. Every sentence adds value.

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?

Despite moderate complexity (6 parameters, nested objects, no output schema), the description lacks details on optional parameters, idempotency, side effects, and error conditions, making it incomplete.

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 compensate by explaining parameters, but it only vaguely mentions 'context'. Parameter names like goal_summary and completed_steps are somewhat self-explanatory but not elaborated.

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 'named memory profile with context', and distinguishes it from sibling tools like browser.get_memory_profile and browser.save_auth_profile by specifying persistence and future loading.

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 usage for persisting session context for later sessions, and hints at the loading mechanism via create_session. However, it does not explicitly exclude use cases or mention alternatives like browser.save_auth_profile.

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