browser.list_memory_profiles

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

No annotations provided, and the description merely restates the tool's name. It does not disclose potential side effects, authentication requirements, or whether the list is session-scoped. For a simple read operation, minimal disclosure is acceptable but insufficient for full transparency.

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, concise sentence that is front-loaded with the action and resource. 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?

For a trivial tool with no parameters and no output schema, the description is minimally complete. However, it does not explain what a 'memory profile' is or how results relate to sessions, which would help an agent using sibling tools like browser.save_memory_profile.

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?

The input schema has 0 parameters with 100% coverage (vacuously). The description adds no parameter information, which is acceptable since there are none to describe. Baseline is 3 per schema coverage.

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 'List all saved memory profiles' uses a specific verb ('List') and a clear resource ('memory profiles'), distinguishing it from siblings like browser.get_memory_profile (single) and browser.save_memory_profile (create).

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 on when to use this tool vs. alternatives such as browser.get_memory_profile or browser.list_auth_profiles. The description lacks context for decision-making.

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