Delete Memory

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

Annotations already flag destructive behavior with destructiveHint=true, and the description matches that. It adds useful behavioral context beyond the annotations by explaining that wait_for_index controls whether deletion waits for secondary indexes before returning and that keyspace defaults to the configured namespace.

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 front-loaded with a one-line purpose followed by a compact Args list. Every clause adds information, and there is no filler or restating of the tool name.

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?

With no output schema, zero schema descriptions, and a destructive operation, the description should define the full input contract. It covers the delete operation and wait_for_index behavior, but leaves scope unexplained and does not clarify the deletion target precondition. DestructiveHint covers the danger, so this is not a complete failure, but it is incomplete.

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. It meaningfully explains keyspace, key, custom_key, and wait_for_index, but it omits the scope parameter entirely and does not clarify whether key/custom_key are alternatives or if at least one is required.

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 opening sentence 'Delete a stored record from memory by key or custom key' names a specific verb, resource, and selection method. It clearly distinguishes this from sibling tools like montycat_remember, montycat_recall, and montycat_remove_keyspace.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description implies deletion of memories, but the agent is left to infer that it should be chosen over related memory tools.

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