workers_memory_delete

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

With no annotations provided, the description carries full burden. It only states 'Delete a memory entry' but does not disclose whether the deletion is permanent, whether it requires authentication, what happens if the message_id does not exist, or if there are any side effects. Behavior is minimally transparent.

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 concise sentence with no wasted words. However, given the complexity of a 3-parameter delete operation with no annotations, it is too terse and misses critical context. Conciseness is achieved at the expense of completeness.

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?

Despite the presence of an output schema, the description lacks usage guidelines, parameter semantics for two optional fields, and behavioral transparency (e.g., irreversibility). For a delete tool with no annotations, the description 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 add meaning. It only mentions message_id, ignoring the optional parameters topic and group_id. Their purpose (e.g., scoping deletion to a specific topic or group) is not explained, leaving the agent to guess.

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 clearly states the action (delete), the resource (memory entry), and the key identifier (message_id). It is specific and easily distinguishes itself from sibling tools like workers_memory_get, workers_memory_add, and workers_memory_edit.

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 guidance is provided on when to use this tool versus alternatives. For example, when to delete versus edit a memory, or any prerequisites like ownership or permissions. The description assumes the agent knows the context without explicit direction.

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