Get Collection Statistics

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds no behavioral context beyond the annotations, such as what happens if the collection does not exist or permission issues. With annotations covering the safety profile, a score of 2 is appropriate as the description provides no additional transparency.

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 a single sentence with no unnecessary words. It is front-loaded and efficient. However, it might be considered too brief given the complexity of the tool, but it 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?

Given the high number of sibling tools and lack of output schema, the description is insufficient. It does not explain what statistics are returned (e.g., document count, size) or the format. While minimal, it lacks completeness for an agent to use effectively without additional context.

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 schema has 100% coverage for the single parameter collId with description 'Collection ID'. The tool description does not add any further semantic meaning for the parameter. Baseline 3 is correct since the schema already documents the parameter adequately.

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 'Get statistics for a collection' clearly states the verb and resource, distinguishing it from sibling tools like transkribus_coll_get_metadata or transkribus_coll_list. However, it does not specify what type of statistics (e.g., counts, sizes), which would enhance clarity.

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 provides no guidance on when to use this tool versus alternatives. For example, it does not clarify that this tool is for aggregate statistics rather than detailed metadata retrieval, or when to use transkribus_stat_get_coll_stats instead.

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