take_heapsnapshot

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

No annotations are provided, so the description carries the full burden. It says nothing about the cost of the operation, even though heap snapshots are typically large, slow, and memory-intensive, nor about permissions, whether the page is paused, or where the file lands relative to the given path.

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?

A single efficient sentence with the action front-loaded and no filler. It is appropriately sized, though the brevity comes partly from omission rather than tightness.

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 an unannotated, no-output-schema tool with meaningful side effects (writing a file) and likely performance impact, the description is too thin. An agent lacks any signal about cost, blocking behavior, or where the snapshot file is written relative to filePath.

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 pageId (defaults to selected page) and filePath are already fully documented in the schema. The description adds no syntax, path-resolution, or format constraints beyond restating the .heapsnapshot extension, matching the baseline for schema-covered parameters.

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?

States a specific verb (capture) and resource (heap snapshot of the page) plus the output artifact (.heapsnapshot file). It is clearly distinguishable from take_snapshot and take_screenshot, though it never names those siblings explicitly, so it stops short of a 5.

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 versus take_snapshot, take_screenshot, or the performance tracing tools. No prerequisites, no exclusions, no context about what scenario a heap snapshot serves.

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