chroma_add_documents

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

The description lacks any behavioral disclosure beyond the basic action. It does not mention whether duplicate IDs cause errors or overwrite, whether documents are validated for size or format, or what the return value indicates. With no annotations provided, the description carries the full burden and fails to address key behavioral traits.

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 structured with an Args block, which is clear, but it largely restates the schema information. While not excessively long, it could be more concise by omitting redundant parameter descriptions and focusing on unique behavioral details.

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 the tool mutates data and has no output schema or annotations, the description is incomplete. It does not explain the return value, constraints (e.g., document count limits), or side effects of adding documents to an existing collection. The agent lacks enough context for reliable use.

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 provides basic semantics for each parameter (e.g., 'ids: List of IDs for the documents (required)'). This adds moderate value beyond the parameter names but lacks depth, such as uniqueness constraints for 'ids' or format expectations for 'documents'.

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 tool adds documents to a Chroma collection, using the verb 'add' and specifying the resource 'documents to a Chroma collection'. However, it does not differentiate from sibling tools like 'chroma_update_documents' or 'chroma_delete_documents', which share similar contexts.

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 instance, it does not state that the collection must exist before adding, nor does it explain when to use 'add' over 'update' or 'delete'. The agent is left without 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.