Add Documents to Collection

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

Annotations already indicate non-read-only, non-destructive, non-idempotent, and open-world behavior. The description adds no behavioral context, such as what happens if a document is already in the collection, side effects, or failure conditions. The open-world hint is not explained.

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, making it concise but lacking necessary detail for a tool with three parameters and multiple siblings. It is front-loaded with the key action but does not earn its place by omitting important information.

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 absence of an output schema, the description should explain what the tool returns. It also does not cover the optional 'moveTo' parameter or conditions like document existence. The tool is simple but the description is insufficient for an agent to use it correctly 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?

Schema coverage is 100%, so the schema already describes the parameters. The description does not add any extra meaning or usage hints beyond what is in the schema, especially for the 'moveTo' parameter. Baseline score of 3 is appropriate.

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 'Add multiple existing documents to a collection' clearly states the verb ('add') and resource ('existing documents' to 'a collection'). It distinguishes from the sibling 'transkribus_coll_add_doc' by specifying 'multiple' documents, but does not elaborate on any limitations or context.

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 given on when to use this tool versus alternatives like 'transkribus_coll_add_doc' for single documents or document creation tools. There is no mention of prerequisites (e.g., documents and collection must exist) or when not to use this tool.

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