Capture a .memgraph from a running process

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

Describes the underlying command (leaks), resolution via pgrep, and the write action. Lacks details on side effects (e.g., process pause) or error handling, but with no annotations, this is a solid disclosure.

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?

Single concise paragraph front-loading purpose and key mechanics. Every sentence adds value; no redundancy.

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 no output schema and no annotations, the description fully covers purpose, parameter usage, constraints, and limitations. Provides complete guidance for an agent.

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 already documents all 3 parameters with 100% coverage. Description adds valuable context: mutual exclusivity of pid and appName, resolution via pgrep, and implicit output extension requirement.

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 captures a .memgraph from a running process using `leaks --outputGraph`. Distinguishes from sibling tools like analyzeMemgraph or diffMemgraphs by focusing on capture.

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 notes it only works on local Mac and iOS simulator, not physical devices, and directs users to Xcode's Memory Graph button for that case. Provides clear when-to-use/when-not-to-use guidance.

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