Delete Memory Snapshots

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

Annotations already mark the tool as destructive, and the description adds valuable context: it destroys snapshot history but preserves loaded in-memory records, and notes that Montycat performs the final authorization check. This goes beyond the annotation and helps set accurate expectations for a mutation operation.

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 compact and well-organized: a one-sentence action statement, a two-sentence caveat about destructive scope and authorization, then a focused Args section. Every sentence earns its place, and the most important information is front-loaded.

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 single-parameter destructive tool with annotations already covering safety hints, the description is complete. It states what the tool does, what it affects, what it does not affect, the authorization step, and the meaning of the one required argument. No critical context is missing.

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%, so the description must compensate for the parameter's meaning. It does so by explaining that keyspace is the 'Explicit in-memory keyspace whose snapshots are cleaned.' This adds key semantic detail beyond the bare property name and type in the input 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?

The description states a specific verb and resource: 'Delete snapshot files for one existing in-memory keyspace.' It also clarifies that it does not delete currently loaded in-memory records, which distinguishes it from siblings like montycat_remove_keyspace. This leaves no ambiguity about the tool's core function.

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 the tool is used to clean snapshot history for a keyspace, and it clarifies the destructive scope, but it does not explicitly state when to prefer this tool over alternatives or mention any exclusions. No sibling tools are referenced for routing decisions.

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