memory_heap_snapshot

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

Discloses important behaviors such as typical file sizes (50-200MB), save directory, and parameter effects (stable_ms, max_wait). Without annotations, this provides good transparency, though could mention performance impact.

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?

Very concise and well-structured: one-liner purpose, then brief context, then parameter explanations. Front-loaded with key information. Every sentence adds value.

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's purpose of capturing a heap snapshot, the description covers the outcome (saved to directory), parameters, and behavior. Even with an output schema, the description is complete for agent understanding.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter: filename (default timestamped), stable_ms (stability condition), and max_wait (hard cap). This adds significant meaning 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 clearly states the tool captures a V8 heap snapshot, specifying the file format and usage. It distinguishes from siblings as no other tool performs this specific function.

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?

Provides context about snapshot size and save location but lacks explicit guidance on when to use this tool over alternatives or when not to use it. The usage is implied but not clearly delineated.

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