Duplicate Document

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

Annotations indicate readOnlyHint=false, but description does not disclose behavior beyond duplication. No mention of side effects, permissions needed, or whether the original document is affected. With no output schema, the return value is also opaque.

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?

Description is extremely short (one sentence) but under-specifies the tool's capabilities. It is not appropriately sized; it loses points for lacking necessary details.

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 4 parameters, no output schema, and sparse annotations, the description is incomplete. It does not explain the duplication destination options, the effect of optional parameters, or what the response contains (e.g., new doc ID).

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 baseline is 3. The description 'Duplicate a document within a collection' adds no additional meaning beyond the schema's param descriptions. It does not clarify optionality of targetCollId or name default behavior.

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?

Description states verb 'Duplicate' and resource 'document within a collection', but is ambiguous about scope: it could mean only within the same collection, yet parameters allow copying to a different collection via targetCollId. It does not differentiate from sibling transkribus_coll_duplicate which duplicates the whole collection.

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 on when to use this tool vs alternatives, prerequisites, or when not to use. For example, no mention of when to use transkribus_coll_add_doc or transkribus_coll_duplicate instead.

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