compare_snapshots

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

Describes taking two snapshots with delay, but does not specify output format (e.g., diff report), side effects, or whether snapshots are saved. No annotations to supplement; adequate but gaps remain.

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, front-loaded with main action, no wasted words. Efficient.

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?

Covers purpose, usage, and parameters adequately. Missing details on output, errors, and behavior. For a 4-parameter tool without output schema, should provide more on what comparison yields.

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 100% provides parameter descriptions. Description adds value by clarifying mutual exclusivity of pid/processName/command and mentions delaySeconds in context, going beyond 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?

Clearly states it takes two snapshots with delay for comparison, useful for leak detection. Distinguishes from sibling 'snapshot' (single) and 'analyze' (analysis). Verb+resource clear.

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?

Explicitly says useful for detecting memory leaks by comparing before/after state. Implies not for single snapshots. Lacks explicit when-not or alternatives but context is clear.

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