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

The description asserts 'Idempotent — a missing row returns deleted=false,' but the annotations declare idempotentHint: false. That is a direct contradiction on a named behavioral hint and will give the agent conflicting signals about safe retry behavior. (The other content — soft-delete with audit history preserved, header-injected identifiers — is genuinely useful, but the contradiction dominates.)

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?

Front-loaded with the action and scope, then organized under 'Use when' and 'Behavior' labels. Slightly fragmented into stubs, but every line carries information and nothing is wasted.

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 an output schema present, return details need not be explained, and the destructive nature is covered by both annotations and the 'Behavior: destructive' line. The description adds soft-delete/audit context and the header-injection note, leaving only the meaning of scope/scope_id under-specified.

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% and neither of the two parameters (scope, scope_id) is documented in the schema; there are no enums to infer from. The description only gestures at the concept ('USER or WORKSPACE scope') and mentions that workspace_id/user_id are injected from headers, but never states the accepted scope values or what scope_id refers to, so it does not compensate for the coverage gap.

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?

States a specific verb and resource with its exact scope: 'Delete the single MEMORY document for a USER or WORKSPACE scope.' It names the sibling it is not (UpsertScopedMemory) and is immediately distinguishable from get_scoped_memory and upsert_scoped_memory.

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?

Gives an explicit trigger ('Use when the user explicitly asks to clear their scoped memory') plus an exclusion and alternative ('Prefer UpsertScopedMemory to update, not delete-then-recreate'). Both when-to-use and when-not-to-use are covered.

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