chroma_delete_collection

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. However, it merely says "Delete a Chroma collection" without stating that the operation is irreversible, requires the collection to exist, or any side effects (e.g., data loss). This is a critical gap for a deletion tool.

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, consisting of one sentence for the tool and one line for the parameter. It is front-loaded with the core action and resource, with no extraneous information. 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?

Despite the tool having only one parameter, no output schema, and no annotations, the description is too sparse. It omits crucial context for a deletion operation, such as whether the action is reversible, what happens to associated data, and what the response looks like. A more complete description would include warnings about irreversibility and conditions for success.

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 has 0% description coverage, so the description must compensate. It adds a brief explanation for the single parameter ("Name of the collection to delete"), which clarifies its role but does not provide additional details like format, validation rules, or examples. This is minimal but sufficient for a simple string parameter.

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 ("Delete") and the resource ("a Chroma collection"), which distinguishes it from sibling tools like chroma_create_collection or chroma_list_collections. The verb and resource are specific and 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?

No guidance is provided on when to use this tool versus alternatives, such as chroma_modify_collection or chroma_fork_collection. There is no mention of prerequisites (e.g., collection must exist) or when not to use it, leaving the agent with limited context for decision-making.

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