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

With no annotations, the description carries the full burden, and it does disclose one genuinely important trait: this is a soft delete that sets status to DELETED rather than destroying data. However, it says nothing about the confirm flag (default false), permissions, idempotency, or what happens if the document is already deleted.

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?

A single sentence with no filler, and the key semantic qualifier (soft-delete) is front-loaded. It is efficient, though arguably too sparse for a mutation tool with an unexplained confirmation gate.

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?

The output schema covers return values and the soft-delete semantics are stated, but for a destructive-intent mutation with no annotations, 0% schema coverage, and an unexplained confirm flag, the description leaves too much for the agent to guess.

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 the description names no parameters at all. The critical 'confirm' boolean with a false default is completely unexplained, so an agent cannot know whether the call actually performs the delete without it.

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 ('delete a document') and qualifies it with 'soft-delete (sets status to DELETED)', which distinguishes it from a hard delete. It does not differentiate itself from siblings like update_document or list_documents, so it lands just short of a 5.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as update_document for status changes. The agent must infer the usage context entirely from the verb in the name.

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