user_storage_manage_delete

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

No annotations are provided, so the description carries the full burden. It does not state that this is destructive and irreversible, nor does it mention the confirmation requirement, which only appears buried in the schema's confirm parameter. For a delete operation with zero annotation coverage, this is a substantial gap.

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?

Extremely compact at four short lines with the HTTP verb and resource front-loaded. It is not wasteful, though it is under-specified rather than merely concise and the Russian tag/spec lines read as generated metadata rather than agent-facing guidance.

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?

A destructive mutation tool with no annotations, no output schema, and no explanation of consequences, permissions, or how it relates to sibling delete endpoints. The description is too thin for the agent to invoke it safely and correctly without opening the schema.

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 the schema already documents name, confirm, and user_id, including the rw-mode preview behavior for confirm. The description adds no parameter meaning beyond the endpoint line, so baseline 3 applies.

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 identifies the operation as a DELETE on /storage/manage and its effect ('Удалить данные в хранилище'), which is clear enough. However it does not distinguish this bulk-delete endpoint from the sibling user_storage_manage_by_name_delete, which deletes by name. The agent can infer intent from the name and path but the description offers no explicit differentiation.

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 on when to use this tool versus user_storage_manage_by_name_delete or the other storage-manage variants. The spec tag 'user' implies a scope but the description never states preconditions, alternatives, or exclusions.

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