capture_snapshot

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

The description says 'point-in-time snapshot,' implying a read-only operation, but with no annotations, it fails to disclose other behaviors such as required permissions, performance impact, or whether the snapshot is destructive. Limited detail is provided beyond the core idea.

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 sentence, which is concise but under-specified. It front-loads the key concept but omits necessary details, making it too terse for complete understanding.

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, no annotations, and two parameters with zero coverage, the description is severely incomplete. It does not explain the output format, how to interpret results, or how parameters affect the snapshot, leaving the agent with insufficient information.

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?

The description has 0% schema description coverage and does not mention the parameters (process_names, pids) or explain how they filter the 'matching processes.' This lack of parameter information makes the tool difficult to invoke correctly without external knowledge.

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 captures a point-in-time snapshot of processes including modules and network connections, distinguishing it from siblings like get_network_connections or get_process_details. However, it does not explain the matching criteria based on the parameters, leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives like get_network_connections or list_processes. There is no mention of use cases, prerequisites, or when not to use it, leaving the agent without context for selection.

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