Get Collection Metadata

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds no further behavioral context, such as whether stats inclusion affects response size or whether metadata is minimal versus full. With annotations covering the main behavioral traits, a 3 is appropriate.

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, clear sentence with no waste. It is front-loaded with the action and resource. It earns a 4 rather than 5 because it does not include a brief note about the optional stats parameter, which could help the agent decide whether to pass it.

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 metadata retrieval with full schema coverage and safety annotations, the description is adequate. However, it does not explain what 'metadata' includes or how the stats flag changes the output, and there is no output schema to clarify the return shape. This leaves minor ambiguity but not critical gaps.

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 both parameters (collId and stats) are already documented in the schema. The description itself adds no additional parameter-level meaning. The 'stats' parameter's effect on response content is not elaborated beyond 'Include statistics', but the schema handles the baseline.

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 metadata for a collection' clearly identifies the verb ('Get') and the resource ('metadata for a collection'), so purpose is clear. However, it does not distinguish itself from sibling tools like transkribus_coll_get_recent_collections, transkribus_coll_list, or transkribus_coll_user_stats, which could also be interpreted as retrieving collection-related information.

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 conveys a straightforward read operation but offers no explicit guidance on when to use this tool over alternatives such as transkribus_coll_list, transkribus_coll_get_recent, or transkribus_doc_get_metadata. The context is clear for a generic metadata fetch, but no exclusions or alternative conditions are provided.

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