browser_perf_take_heap_snapshot

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

No annotations are provided. The description says 'Capture heap snapshot', implying a potentially heavy operation, but does not disclose side effects (e.g., memory consumption, performance impact, or whether it modifies state). It relies on browser_docs for details, which is insufficient for standalone 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 extremely concise, one sentence with a cross-reference. It is well-structured and front-loaded, but could be slightly more informative without sacrificing brevity (e.g., mentioning output format).

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?

The tool has no output schema and the description does not explain the return value (e.g., a snapshot file, object, or data structure). Given the potentially large resource impact, the description should mention duration, size expectations, or how to retrieve results. The cross-reference to browser_docs partially compensates, but is not 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 has 100% description coverage for its single parameter 'reportProgress', which already explains its purpose. The description adds no additional meaning beyond what is in the schema, so a baseline 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 the action ('Capture heap snapshot') and its purpose ('memory analysis'). It distinguishes from sibling tools like browser_perf_get_heap_usage and browser_perf_get_metrics by using the specific verb '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 implies usage for memory analysis but does not explicitly state when to use this tool versus alternatives like browser_perf_get_heap_usage or browser_docs. The reference to 'see browser_docs' suggests additional guidance, but the description itself lacks direct when/when-not instructions.

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