List Collections (XML)

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description's only added behavioral fact is the XML output format, which is genuinely useful since it is not in the annotations. Nothing is said about pagination defaults, result size, or auth requirements.

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; the format qualifier is placed where it matters. It is tight but borderline under-specified rather than merely concise.

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 4-parameter list tool with no output schema, the definition is minimal. The claim 'List all collections' is ambiguous against an nValues default of 0, and there is no mention of pagination behavior or the shape of the XML response, leaving real gaps for correct invocation.

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 four parameters (index, nValues, sortColumn, sortDirection) are already documented in the schema. The description adds no parameter meaning — notably it never explains that nValues=0 is the default or how it interacts with 'List all'.

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 states a specific verb and resource ('List all collections') and adds a distinguishing output-format qualifier ('in XML format'), which sets it apart from the plain transkribus_coll_list sibling. It does not, however, explicitly name that sibling or scope the listing (e.g., all vs. owned/for-user), so differentiation is inferential rather than stated.

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?

There is no guidance on when to use this over transkribus_coll_list, transkribus_coll_list_paged, transkribus_coll_list_for_user, or transkribus_coll_list_by_name. The agent must infer that 'XML format' is the only selection criterion, and no exclusions or prerequisites are given.

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