Add Document to Collection

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

Annotations are present (readOnlyHint=false, destructiveHint=false) and consistent with the description, but the description adds no additional behavioral context beyond what annotations provide. It does not explain side effects like move vs copy or permissions required.

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 extremely concise (one sentence) and front-loaded with the purpose. It is efficient, though it could be slightly expanded to cover key details without losing conciseness.

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 tool has 4 parameters (including a move flag and an extra docId) and no output schema, the description is too sparse. It does not clarify the difference between 'docId' and 'id', the effect of 'moveTo', or the expected outcome. More context is needed for complete usage.

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?

Input schema provides full coverage (100%) for parameters, so the baseline is 3. The description does not add any extra meaning or explanation for parameters like 'moveTo' or the redundant 'id' field, which could clarify functionality.

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 an existing document to a collection' clearly states the action and resources involved. It is specific enough to distinguish from many sibling tools, but it does not explicitly differentiate from the similar 'transkribus_coll_add_docs' (plural) which likely adds multiple documents.

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 provided on when to use this tool versus alternatives like 'transkribus_coll_add_docs' or 'transkribus_coll_remove_doc'. There is no context on prerequisites, suitability, or when not to use it.

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