browser.save_memory_profile

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

Annotations already indicate non-read-only, non-destructive, non-idempotent behavior. The description adds no further behavioral details (e.g., whether overwriting occurs, concurrency, or side effects). Description is adequate but doesn't go beyond annotations.

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?

Two concise sentences, front-loaded with core action, no unnecessary words. Information is efficiently delivered.

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 6 parameters, no output schema, and moderate annotations, the description provides enough for basic understanding. However, it could be more complete by explaining the purpose of optional fields and return values. Still, it covers the primary use case.

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 0%, so burden on description to explain parameters. The description only mentions 'context from the current session' without detailing the six parameters (session_id, profile_name, goal_summary, etc.). The parameter names are somewhat self-explanatory, but the description adds minimal value.

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?

Clearly states the tool saves a named memory profile with session context, and explains its purpose for future sessions. Distinguishes itself from sibling tools like get_memory_profile and list_memory_profiles.

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?

Describes when to use (to save context for later sessions) and how to use ('Loaded into future sessions via memory_profile=name'), but does not explicitly state when not to use or compare to alternatives like save_auth_profile.

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