snapshot

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

No annotations are provided, so the description carries full burden. It mentions waiting before capture but fails to disclose side effects (e.g., whether the process is paused, memory impact, or if the snapshot is saved/returned). The agent lacks behavioral context for safe usage.

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 two sentences with no wasted words. It front-loads the purpose and then provides parameter hints. Every sentence is earned.

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?

The description covers input parameters adequately but lacks information about output (e.g., what is returned after snapshot). Given no output schema and the existence of sibling tools like compare_snapshots and analyze, the agent needs to know how to use the snapshot result.

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 description adds value by clarifying that pid, processName, and command are mutually exclusive alternatives, and that durationSeconds is optional. This grouping information is not present in individual schema descriptions.

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 it takes a memory snapshot of a .NET process. The verb 'Takes' combined with resource '.NET process' makes the purpose unambiguous. It also distinguishes from sibling tools like list_processes or compare_snapshots.

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 provides implicit guidance on using one of pid, processName, or command, and optionally durationSeconds. However, it does not explicitly state when to use this tool versus alternatives (e.g., when to use compare_snapshots instead) or any exclusion criteria.

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