insert-many

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds a useful performance constraint about payload size limits, but does not address other behavior like partial insert failures or ordering. No contradiction with annotations.

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 exactly two sentences. The first states the purpose directly; the second gives a specific operational tip. No wasted words, and the key information is 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 simple 3-parameter insert tool with an output schema, the description covers the main action and an important operational constraint (batching for large arrays). It does not need to explain return values because an output schema exists. The only minor gap is lack of guidance on when to choose this over alternatives, but the tool is self-explanatory.

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 each parameter (database, collection, documents) already described in the schema. The tool description only paraphrases 'array of documents' without adding new parameter-level information, so it stays at the baseline for high coverage.

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 says 'Insert an array of documents into a MongoDB collection,' which is a specific verb+resource statement. It clearly distinguishes this from sibling tools like delete-many, update-many, and aggregate by naming the exact operation and target.

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 provides a clear usage guideline for large payloads: 'If the list of documents is above com.mongodb/maxRequestPayloadBytes, consider inserting them in batches.' This gives the agent actionable context, though it does not explicitly mention alternatives or when-not-to-use scenarios.

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