Delete non-production MongoDB documents

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds genuinely new behavioral context beyond the structured data: the environment gate (non-production only, production always blocked) and the allow_all precondition for empty filters. Auth requirements and return behavior remain unstated.

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?

Two tight sentences: the action is front-loaded, then the two gating constraints follow. No filler, no repetition of the title or annotations.

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 destructive tool with 0% schema coverage and no output schema, the description covers the critical safety rules but omits what the operation returns (count of deleted documents?) and the meaning of connection_id/collection/response_format. Adequate for a guarded delete, but not fully self-contained.

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% across 5 parameters, so the description carries the burden. It clarifies the filter/allow_all interaction, which is real semantic value, but leaves collection, connection_id, and the response_format enum undocumented. Partial compensation only.

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+resource ('Delete matching documents') and adds a scope qualifier ('from a non-production collection') that inherently separates it from mongo_find, mongo_update_many and mongo_insert_one. Sibling tools are not named explicitly, but the verb and environment restriction make the intent unambiguous.

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?

Provides two concrete operational rules: empty filters require allow_all=true, and production is always blocked, telling the agent when the call will be refused. It lacks explicit guidance pointing to alternatives (e.g. mongo_update_many when the intent is modification), so it falls short of a 5.

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