delete_document

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to clarify whether the tool deletes a single document or all documents matching the filter query, what happens on no match, whether the operation is reversible, permission requirements, or what response is returned. The ambiguous 'matching document' leaves critical safety behavior unspecified.

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 terse sentence with no fluff, but it is under-specified. It lacks essential details needed for safe and correct usage, so it is not appropriately sized. The phrase 'matching document' is ambiguous and does not earn its place over a more informative description.

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 no annotations, no output schema, and zero schema description coverage, the description is severely incomplete. It does not explain return values, error behavior, scope of deletion, or any operational nuances. The 2-parameter tool needs much more context to be used correctly by an agent.

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 provides no parameter explanations. The schema shows collection_name and filter_query types but no semantics for filter_query structure or how it is used. 'Matching' is the only hint, but it does not clarify the filter query format, matching logic, or limits.

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 ('Delete') and resource ('matching document'), and 'matching' implies the filter_query parameter. It is distinguishable from siblings like find_document, update_document, and insert_document. However, it does not explicitly mention the collection context, relying on the schema parameter collection_name.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention when deletion is appropriate, prerequisites, or contrast with find_document or update_document. It simply states the action without context.

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