Get User Stats

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — it does not explain pagination via index/nValues, what sorting does, or what the statistics contain, leaving the tool's behavior opaque for a multi-param query endpoint.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though arguably too terse given the tool's complexity — there is no wasted text, but also no useful text beyond the minimum.

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 five-parameter statistics endpoint with no output schema, the description should at least indicate what statistics are returned (per-user counts, roles, activity) and how index/nValues paginate the result. None of that is present, so an agent knows the surface but not the payload.

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%, so all five parameters (index, collId, nValues, sortColumn, sortDirection) are already documented in the schema. The description contributes no additional parameter meaning, which is the expected baseline 3 when the schema does the work.

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 names a specific verb and resource ('Get user statistics') scoped to a collection, which is more than a tautology. However, it does not differentiate from close siblings such as transkribus_user_get_stats, transkribus_coll_user_count, transkribus_coll_user_list, or transkribus_stat_get_coll_stats, so an agent cannot tell which of these to pick from the text alone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling stats/count tools. The agent must infer usage purely from the tool name.

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