take_memory_snapshot

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

The annotation already flags this as not read-only. The description adds that it captures a snapshot and saves to a file, but omits behavioral details like potential page freeze, performance impact, or whether it requires a loaded page. This is adequate but not rich.

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 extremely concise with two sentences, no redundant words. The purpose is front-loaded, making it easy for an AI agent to quickly grasp the tool's function.

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 tool has one required parameter and no output schema, the description adequately covers what it does. However, it does not mention what the result is after saving (e.g., no return value). For a simple tool, this is mostly complete.

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 covers the parameter with full description. The tool description adds no additional meaning beyond what the schema provides. With 100% schema coverage, a score of 3 is appropriate.

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 that the tool captures a heap snapshot of the selected page for memory analysis. It uses specific verbs and resources, but it does not differentiate from the sibling tool 'take_snapshot', which might be confused with a visual snapshot.

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 indicates usage for debugging memory leaks, which is clear. However, it lacks guidance on when not to use it or mention of alternatives like performance profiling tools. No prerequisites or context on page state are provided.

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