delete_one

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

The destructiveHint annotation already flags this as destructive. The description adds useful behavioral context beyond the annotation by specifying that exactly one document is removed and that it is the first match for the filter. It does not discuss irreversible consequences or no-match behavior, but the annotation and wording cover the core trait.

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, front-loaded Indonesian sentence communicates the core behavior with no filler. Every word earns its place, and the most important qualifier ('SATU') appears immediately.

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 destructive single-document deletion tool, the description plus complete schema and destructiveHint annotation is nearly sufficient. It is missing minor details such as behavior when no document matches, but an agent can invoke the tool correctly from the provided information.

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 schema already documents filter, database, and collection. The main description adds little beyond what the schema says; it reinforces the meaning of 'filter' but does not introduce new parameter semantics.

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 has a specific verb ('Hapus'), a specific resource ('satu dokumen'), and a clear scope ('pertama yang cocok dengan filter'). The word 'SATU' explicitly distinguishes it from the sibling delete_many, so an agent can select it correctly.

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 clearly implies when to use it: to delete a single first-matching document. It does not explicitly name alternatives or exclusions like 'for multiple documents, use delete_many', but the single-document qualifier provides sufficient contextual guidance.

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