cross_validate_processes

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

No annotations are provided, so the description carries full burden. It discloses the output behavior ('returns ghost processes') and implies a non-mutating comparison, but does not mention prerequisites (e.g., prior output from vol_pslist/vol_psscan), error conditions, or side effects.

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?

One concise sentence front-loads the core action and result. Every word is purposeful with no redundant content, making it highly 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?

For a tool with two string parameters and an output schema, the description provides the essential purpose but lacks usage guidance and prerequisite context. It is minimally sufficient but leaves gaps around when to invoke and how inputs should be prepared.

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 0%, yet the description only rephrases the parameter names ('pslist vs psscan artifacts') without adding format, source, or usage details. The agent gains little beyond what the parameter names already convey.

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 a specific action: 'Compare pslist vs psscan artifacts' with a distinct outcome ('returns ghost processes'). It differentiates from siblings like vol_pslist and vol_psscan by focusing on cross-validation rather than standalone listing.

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?

Usage is implied through the comparison of two artifacts, suggesting it is used when investigating hidden processes. However, it does not explicitly state when to choose this over alternatives or when not to use it, lacking clear exclusions or prerequisites.

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