delete_agent_memory

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'soft delete' qualifier adds valuable nuance beyond the structured metadata. It clarifies that the operation is not a hard permanent removal, though it does not explain recoverability or downstream visibility.

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 short and front-loaded with the core action and soft-delete behavior. The 'Requer...' sentence is slightly redundant with the required parameter list, but it serves as an at-a-glance checklist without adding unnecessary length.

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 simple three-parameter destructive operation, the description and annotations give enough context to invoke it correctly. Return-value expectations are not specified, but for a delete-style tool without an output schema this is a minor gap; clarifying soft-delete consequences would make it more complete.

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 100%, so each parameter is already documented. The description only repeats the parameter names without adding format, selection, or usage details beyond what the schema provides, making baseline 3 appropriate.

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 names a specific action ('Remove (soft delete)') and a specific resource ('uma memória específica de um agente'), which clearly distinguishes it from deleting an entire agent or listing memories. It does not explicitly mention sibling tools, but the object and scope are clear enough.

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 such as list_agent_memory or delete_agent. The description only restates the required parameters without providing selection criteria or exclusions.

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