memory_leak_heap_snapshot_differ

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

With no annotations, the description carries the full burden. The verb 'Diffs' implies a non-mutating analysis operation, and the parenthetical price transparently discloses cost. However, it does not describe side effects, data handling, input requirements, or output behavior beyond the broad 'isolate' language.

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 a single, front-loaded sentence that conveys the operation, target issues, and context. The cost disclosure is parenthetical and non-intrusive. Every part earns its place with no filler.

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 a tool with no annotations, no output schema, and a highly generic payload parameter, this description is under-specified. It tells an agent why to use the tool but not how to construct a valid payload or what the result will look like. An agent could select the tool but would struggle to invoke it correctly without external assumptions.

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%, but the payload schema is generic boilerplate ('Input parameters or JSON string payload'). The description adds some domain meaning by indicating the payload relates to V8 heap snapshots, but it never specifies how snapshots should be encoded, how many are expected, or what fields are needed.

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 opens with a specific verb and resource: 'Diffs V8 heap snapshots'. It then names concrete goals (detached DOM elements, uncleared event listeners, uncollected closures), making the tool's role unmistakable and distinct from the large list of unrelated siblings.

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 ties the tool to a clear scenario: diagnosing 'long-running agent OOM crashes' via heap snapshot diffing. It does not explicitly name exclusions or alternative tools, but the domain is narrow enough that an agent can infer when it applies.

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