Get Collection Stats (New)

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no behavioral context beyond mentioning a 'new stats endpoint,' but it does not contradict the annotations.

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 short sentence that front-loads the purpose. The phrase 'new stats endpoint' is somewhat vague and time-sensitive, but overall the description is concise and easy to consume.

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 read-only single-parameter tool, the description is minimally adequate, but it lacks detail about what statistics are returned and how this differs from transkribus_stat_get_coll. With no output schema, the description would benefit from clarifying the scope or content of the statistics.

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?

Schema description coverage is 100%, and the sole parameter collId is documented as 'Collection ID' with an integer type and valid range. The description adds no additional parameter semantics, so the baseline score of 3 applies.

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 a specific verb and resource: get collection statistics. It is vague about what statistics are included and does not explicitly differentiate from sibling tools like transkribus_stat_get_coll, but it does convey the core operation adequately.

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 about when to use this tool versus the many sibling statistics tools such as transkribus_stat_get_coll, transkribus_coll_user_stats, or transkribus_stat_get_storage_usage. The phrase 'new stats endpoint' hints at a version distinction but does not explain when it should be preferred.

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