Remove Document from Collection

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

Annotations already declare the operation as destructive and idempotent, so the description does not need to restate those. It adds one useful behavioral clarification: the document itself is not deleted. However, it does not mention side effects, error behavior, or reversibility beyond what the annotations already imply.

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 that uses every word effectively. It front-loads the core action and immediately clarifies the important non-destructive aspect.

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 two-parameter mutation, the description plus schema and annotations are mostly sufficient for an agent to invoke it correctly. The main gap is the lack of routing context to distinguish it from the nearly identical sibling transkribus_doc_remove_from_collection, which prevents a perfect score.

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%, with both 'id' and 'collId' already documented. The description adds no further parameter meaning, so it does not improve on what the schema provides. The baseline of 3 is appropriate because the schema carries the representational burden.

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 the action: remove a document from a collection, and adds the key qualifier 'without deleting it,' which distinguishes it from document deletion. However, it does not differentiate this tool from the very similar sibling transkribus_doc_remove_from_collection, so it is not fully distinct among siblings.

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 offers no explicit guidance on when to use this tool versus alternatives such as transkribus_doc_remove_from_collection, transkribus_doc_delete, or transkribus_coll_delete. The phrase 'without deleting it' implicitly suggests it is not for permanent deletion, but no alternatives or selection criteria are named.

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