disk_parse_srum

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

With no annotations provided, the description carries full burden but only states what data it extracts. It does not disclose whether the tool is read-only, requires administrative privileges, or has performance implications, leaving the agent unaware of potential 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?

The description is short (two sentences), front-loaded with the verb 'Parse', and contains no redundant information. Every sentence adds value.

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 the tool has 6 parameters and no output schema, the description adequately conveys the high-level purpose but lacks details about return format or structure of the parsed data, which would help the agent understand what to expect.

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 input schema has 100% description coverage, so each parameter is well-documented. The tool description adds context about the overall resource usage questions but does not enhance understanding of individual parameters beyond what schema already provides.

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 parses SRUDB.dat for application resource usage including CPU time, network bytes, and foreground time. It also frames the output as answers to specific questions, distinguishing it from sibling disk parsing tools like disk_parse_amcache or disk_parse_mft.

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 implies when to use the tool (when needing application resource usage from SRUM), but it does not explicitly state when not to use it or mention alternatives among siblings, such as using disk_parse_prefetch for execution history.

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