heap_live_histogram_diff

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

With no annotations, the description fully carries the burden. It warns that 'Each snapshot walks the heap and may pause the app.' and the `all` parameter description adds 'Triggers full GC and may pause the app.'

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, each earning its place. First sentence states purpose and mechanism; second provides usage workflow and behavioral note. No wasted words.

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 5 parameters and no output schema, the description covers core functionality, usage guidance, and disruption warnings. However, it does not detail the return format (e.g., fields per class or ordering), which could be improved.

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 80%, with only topN missing a description. The description implies topN limits returned classes ('...whose instance count grew most'), partially compensating. It also adds context about the `all` parameter's behavior.

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 'Two GC.class_histogram snapshots spaced by intervalSeconds; returns classes whose instance count grew most.' This provides a specific verb and resource, distinguishing it from siblings like heap_histogram (single 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 explicitly says 'Use first in memory-leak workflow; then profile_memory and heap_dump (MAT path-to-GC-roots).' This gives clear context and alternative tools for subsequent steps.

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