get_heap_snapshot

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

The description discloses key behaviors: the snapshot is large, written to a .heapsnapshot file, and the file path is returned. Since no annotations are provided, the description carries the full burden and does so adequately.

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?

Two sentences with no wasted words. The main action and key behavioral notes are front-loaded, making it easy for an agent to quickly grasp the tool's purpose.

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 3 parameters (1 required), no output schema, and no annotations, the description covers the essential aspects: what it does, the output format, and parameter defaults. It is sufficient for an agent to decide to invoke it.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the default for 'pageId' (main) and noting that 'filePath' defaults to a temp dir, which aids in understanding parameter behavior beyond 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 uses a specific verb ('Take') and resource ('V8 heap snapshot'), and names the target (main process or renderer page). It clearly distinguishes from siblings like 'get_dom_snapshot' which captures a different type of 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 does not provide when or when not to use this tool versus alternatives. For example, it doesn't contrast with 'get_dom_snapshot' or suggest typical scenarios like memory profiling versus DOM inspection.

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