browser_enrich_memory_async

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

The description adds behavioral context beyond annotations: it reveals the async queueing behavior, immediate task_id return, background URL visit, and a 100-credit cost. This complements the annotations (readOnlyHint=false, openWorldHint=true) without contradicting them, though it doesn't discuss failure modes or task tracking.

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 sentences, front-loads the core action ('Queue an async browser memory enrichment task'), and every clause adds useful information (task_id, background, ZeroMemory, credits). No wasted words.

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 the async nature and no output schema, the description appropriately highlights the immediate task_id return and background processing. It lacks details on how to track task completion or handle errors, but for a simple queue operation, the core flow is adequately covered. Sibling tools may fill the tracking gap.

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 baseline is 3. The description does not add meaningful detail about parameters beyond referencing URL and ZeroMemory store; it doesn't explain memory_type or extract_goal. It adds minimal value over the schema.

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 tool queues an async browser memory enrichment task, returns a task_id immediately, and stores content in ZeroMemory in the background. The 'async' and 'background' wording distinguishes it from the likely synchronous sibling browser_enrich_memory.

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 non-blocking enrichment by mentioning immediate task_id return and background execution. However, it does not explicitly state when to use this over sibling tools like browser_enrich_memory or browser_extract, but the async nature is a clear contextual signal.

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