memory_delete_batch

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

No annotations provided. The description states 'delete' implying destructive action, but it does not disclose potential side effects, permission requirements, irreversibility, or error handling for partial failures in batch operations.

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 a single short sentence, front-loaded and efficient. It could be slightly more informative without adding much length, but it is concise.

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?

Although an output schema exists (not shown), the description does not cover important batch behaviors like atomicity, partial success, or result format. The tool is simple but lacks necessary details for complete agent understanding.

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 single parameter 'ids' is an array of integers with no schema description (0% coverage). The description only says 'by id' and does not explain constraints like min/max number of IDs, validation, or format requirements beyond the 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 'Delete multiple memories by id' clearly states the action (delete), resource (memories), and scope (multiple, by id). It distinguishes from siblings like memory_delete (single) and memory_create_batch.

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 explicit when-to-use or when-not-to-use is given. It is implied that this tool is for deleting multiple memories by ID, but there is no mention of alternatives like memory_delete for single deletions or batch size limits.

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