mongo_insert_one

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

No annotations are provided, so the description must convey behavioral traits. It discloses that the tool is blocked in readOnly mode, which is important. But it omits details like authentication needs, error behavior, or whether it returns the inserted document's ID.

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 with two short sentences, front-loading the core action. Every sentence serves a purpose without superfluous text.

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 there is no output schema and 4 parameters, the description lacks explanation of return values (e.g., inserted document ID), error conditions, or the purpose of the database and connectionId parameters. It provides minimal context for a write operation tool.

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?

The input schema covers 50% of parameters with descriptions (document and connectionId). The tool description adds no additional parameter information beyond the schema, leaving database and collection parameters undefined. It does not compensate for the missing 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 the action ('Insert a single document') and the target resource ('into a MongoDB collection'). This distinguishes it from sibling tools like mongo_insert_many (insert multiple documents) and read-only tools.

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 mentions it is blocked when readOnly mode is enabled, providing a key condition for non-usage. However, it does not explicitly guide when to use this tool over similar write tools (e.g., mongo_update_one) or describe prerequisites.

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