delete-many

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive write operation. The description adds valuable context by specifying it removes 'all documents that match the filter' (not just one) and references MongoDB's deleteMany() syntax, which helps anticipate behavior. However, it doesn't mention permissions needed, atomicity, or what happens on empty filters.

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, efficient sentence that front-loads the core action ('Removes all documents') and includes essential technical context (MongoDB collection, filter matching deleteMany syntax). Every word earns its place with no redundancy.

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 good annotations (destructiveHint=true) and full schema coverage, the description is reasonably complete—it clarifies scope and references MongoDB syntax. However, without an output schema, it doesn't describe return values (e.g., deletion count), and it lacks guidance on error conditions or permissions, leaving some gaps for a high-stakes 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 100%, with clear descriptions for database, collection, and filter parameters. The description adds marginal value by mentioning the filter 'matches the syntax of db.collection.deleteMany()', but doesn't provide additional syntax examples or constraints beyond what the schema already documents.

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 the action ('Removes all documents'), the resource ('from a MongoDB collection'), and the scope ('that match the filter'), distinguishing it from siblings like drop-collection (which removes the entire collection) or update-many (which modifies rather than deletes).

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 implies usage for deleting multiple documents based on a filter, but doesn't explicitly state when to use this vs. alternatives like drop-collection (for entire collections) or update-many (for modifications). No guidance on prerequisites or exclusions is provided.

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