es_delete_document

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

With no annotations, the description carries the full burden. It correctly signals destructive behavior and the mandatory confirmation flag, which is useful. However, it does not mention irreversibility, behavior when the document does not exist, or any session-related effects.

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 focused sentence with no fluff. It states the action first and immediately follows with the critical safety condition. Every word earns its place.

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 tool is simple and has an output schema, so return details are not needed. The critical confirmation requirement is present, and required parameters are identifiable. Still, without annotations, the description leaves out important behavioral context such as permanence and error behavior.

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 compensate. It adds meaning to confirm by stating it is required, which goes beyond the schema's default of false. index and doc_id are self-explanatory from their names, but session_name remains unexplained.

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 a specific verb and resource: 'Delete one Elasticsearch document.' This distinguishes it from siblings like es_search, es_index_document, mongo_delete, and redis_delete by specifying the exact system and operation.

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?

The description gives an explicit prerequisite: 'confirm=true is required.' This tells the agent how to safely invoke the tool. It does not explicitly contrast with alternative tools, but the operation itself makes the use case clear.

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