mongo_delete_many

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

No annotations provided. The description adds one behavioral note (blocked in readOnly mode) but lacks other important details like irreversible deletion, impact on indexes, or confirmation requirements.

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?

Single sentence, no redundant words. Efficiently conveys the core action and a key constraint.

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?

No output schema, no annotations, and minimal parameter detail. Does not explain return values, error conditions, or behavior when filter matches zero documents, leaving significant gaps for a delete operation.

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 50%. The description adds no parameter-specific information beyond what is already in the schema, missing opportunities to elaborate on filter format or database/collection context.

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?

Description clearly states the action ('Delete multiple documents') and the resource ('MongoDB'), and distinguishes from sibling mongo_delete_one by specifying 'multiple'.

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?

Mentions a condition ('Blocked when readOnly mode is enabled'), but does not explicitly compare to alternatives like mongo_delete_one or explain when to use this tool over others.

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