mongo_update_many

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

No annotations exist, so the description carries full burden for behavioral disclosure. It only mentions 'Blocked when readOnly mode is enabled', indicating it's a write operation and won't work under read-only. But it omits return value, atomicy, error behavior, or side effects (e.g., if filter matches none). For a mutating tool, this is insufficient.

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 extremely concise: two sentences with no fluff. The first sentence tells the core functionality, the second adds a key constraint. Every word earns its place, making it efficient for an AI agent to parse.

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?

Given 6 parameters, no output schema, and no annotations, the description is too minimal. It does not cover return format (e.g., number of modified documents), parameter behavior (JSON strings, upsert default), or error scenarios. For a database modification tool, this lacks critical context an agent would need to invoke it correctly.

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% (filter, update, connectionId have descriptions; upsert, database, collection do not). The description adds no extra meaning beyond the schema—it does not explain how filter/update strings are interpreted (e.g., MongoDB query syntax), the effect of upsert, or the role of database/collection. It fails to compensate for missing schema descriptions.

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 'Update multiple documents matching filter in MongoDB', which specifies the verb (update), resource (multiple documents), and scope (MongoDB). It distinguishes from siblings like mongo_update_one (single) and mongo_delete_many (delete). However, it does not explicitly contrast with other update tools, missing a chance to improve differentiation.

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 like mongo_update_one, mongo_insert_many, or mongo_delete_many. The only extra note is 'Blocked when readOnly mode is enabled', which is a constraint not a usage guide. The description lacks when-to-use, when-not-to-use, or alternative references.

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