chroma_get_collection_count

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

No annotations are provided, so the description bears full burden. It merely restates the obvious action without disclosing return format, error handling (e.g., missing collection), or side effects. This is a serious gap for a tool that returns a computed value.

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 very concise and front-loaded with the purpose sentence. However, it is overly minimal and could include more details in the same space (e.g., return type). It is acceptable but not exemplary.

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 low complexity (1 param, no output schema), the description fails to specify the return format (e.g., integer, JSON object) or behavior on errors. The agent lacks sufficient information to confidently invoke and parse results.

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 should add meaning to the lone parameter. It says 'Name of the collection to count,' which slightly clarifies purpose but repeats the schema title. No additional constraints, formats, or examples are provided.

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 'Get the number of documents in a Chroma collection' with a specific verb and resource. It uniquely identifies the tool's function and distinguishes it from siblings like chroma_list_collections (list collections) and chroma_get_collection_info (get info).

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 on when to use this tool versus alternatives, such as chroma_get_collection_info which might also provide count information. There are no prerequisites, exclusions, or context for optimal usage.

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