insert_many

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

No annotations are present, so the description carries the full burden. It only restates the basic write operation and gives no detail about behavior beyond insertion, such as atomicity, error handling, duplicate behavior, or return values.

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?

A single, focused sentence communicates the core purpose without unnecessary words. The bulk aspect is front-loaded and the sentence is easy 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?

For a simple bulk insert tool, the core action is clear and schema covers parameters. However, with no annotations and no output schema, the description omits usage guidance and behavioral expectations, leaving an agent without enough context to predict side effects or return behavior.

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%, so the input schema already documents all three parameters. The tool description adds no additional parameter-level meaning, which matches the baseline for high schema 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 states a specific action ('insert many documents at once') and a clear target resource ('collection'). The word 'BANYAK' differentiates this from the sibling insert_one, making the tool's bulk purpose immediately obvious.

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 phrase 'BANYAK dokumen sekaligus' implies this tool is for bulk insertion, but it does not explicitly state when to prefer this over insert_one or mention any exclusions. Guidance is implied rather than directly provided.

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