memory_snapshot_delete

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

Annotations declaratively provide destructiveHint=true and idempotentHint=true. The description 'Delete a snapshot' aligns with annotations but adds no extra behavioral context (e.g., irreversibility). Since annotations already cover safety, score is adequate but not elevated.

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?

Single sentence with no wasted words. Front-loaded and 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 single-parameter, no-output-schema tool with good annotations, the description is mostly complete. However, it could mention that the operation is permanent or that snapshots are isolated resources, but given the simplicity, it's adequate.

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 covers 100% of parameters with a clear description for snapshot_id. The tool description adds no additional meaning beyond what the schema already provides, so baseline score applies.

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 the action ('Delete') and resource ('a snapshot'). It distinguishes from sibling tools like memory_snapshot_create, memory_snapshot_list, and memory_snapshot_restore.

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 context on when to use this tool versus alternatives. No mention of prerequisites, consequences, or when not to use. The one-sentence description offers no guidance.

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