list_crash_dumps

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

No annotations are provided, so description carries full burden. It details the types of dumps included (kernel minidumps, full dump, live kernel reports, application dumps, Windows Error Reporting), adding behavioral depth. However, it does not mention whether administrative privileges are needed or performance impact.

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?

Description is front-loaded with primary purpose and well-structured across two paragraphs. Each sentence adds value, though the second paragraph could be slightly tighter.

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?

Description covers multiple dump locations and links to inspect_crash_dump. Missing parameter documentation is the main gap; but given output schema existence and simple parameter, it is largely adequate for selecting the tool.

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?

There is one parameter (limit) with schema documentation 0%. The description does not mention the limit parameter or its meaning, failing to add value beyond the bare schema.

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?

Description clearly states 'List crash dumps on this machine, newest first' with specific verb and resource. It enumerates coverage across multiple dump locations and explicitly distinguishes from sibling tool inspect_crash_dump.

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?

Description advises to pass a path from the list to inspect_crash_dump, providing clear usage context. However, it does not explicitly state when to avoid this tool or name alternatives beyond the sibling mentioned.

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