Update non-production MongoDB documents

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the mutation risk is covered. The description adds genuinely new guardrail context beyond the annotations: the allow_all escape hatch for empty filters and the hard production block. It omits any statement of scope of effect or return behavior.

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 short sentences, zero filler, with the collection scope and the safety preconditions front-loaded.

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, 6-parameter mutation with 0% schema coverage and no output schema, the description covers the critical safety guardrails but leaves most parameters and the return/response_format behavior undocumented. It is adequate on risk, thin on mechanics.

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, yet it only explains 'filter' (in the empty-filter case) and 'allow_all' with a real precondition. The update document, collection, connection_id, and response_format parameters are left entirely 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?

States a specific verb+resource ('Update matching documents') plus a scoping qualifier ('in a non-production collection'), which cleanly separates it from siblings like mongo_delete_many, mongo_insert_one, and mongo_find.

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?

Gives clear conditional guidance: empty filters require allow_all=true and production is always blocked, so the agent knows when the call will be rejected. It stops short of naming alternative tools for out-of-scope cases (e.g., what to use against production), so it is clear but not fully routing.

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