chroma_delete_documents

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

The description lists error conditions (empty ids, missing collection) and mentions it returns a confirmation message, but it does not state that the operation is irreversible or discuss side effects. Given no annotations, more behavioral details could be added.

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 concise and well-structured with a clear purpose statement followed by parameter, return, and error sections. Every sentence adds value without redundancy.

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 deletion tool with two required parameters, the description covers purpose, parameters, returns, and errors. However, it omits details on permanence, handling of non-existent IDs, and usage context, leaving some gaps.

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?

With 0% schema description coverage, the description compensates by explaining the purpose of each parameter: 'collection_name' is the collection's name, 'ids' are document IDs. While basic, it adds necessary meaning beyond the schema's titles.

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 begins with 'Delete documents from a Chroma collection,' which is a specific verb-resource combination that clearly differentiates from sibling tools like adding, querying, or listing documents.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention prerequisites (e.g., obtaining IDs via get_documents) or when deletion is appropriate, which is critical given 12 siblings.

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