mongo_delete_one

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

Discloses the destructive nature and the readOnly blocking condition, but lacks details on irreversibility, behavior with multiple matches (only deletes first), or required permissions. Without annotations, more detail would improve transparency.

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 sentences, no redundancy, front-loaded with purpose. Every word earns its place.

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?

Minimally complete for a simple delete action. Lacks return value, error conditions, and filter format details. Could be improved but acceptable given low complexity.

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?

Description adds no parameter information beyond the schema, which covers 50% of parameters with descriptions. Does not compensate for missing schema descriptions for 'database' and 'collection'.

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?

Description clearly states the verb 'delete' and the resource 'a single document matching filter', distinguishing it from sibling tools like mongo_delete_many. The action is unambiguous.

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?

Implies usage for deleting one document but does not explicitly state when to choose this over alternatives like mongo_delete_many. The readOnly note provides a constraint but not a selection guideline.

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