Duplicate Collection

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

Adds little beyond annotations. Does not explain what duplication entails (e.g., copies content, structure, permissions). Annotations already indicate it's not read-only, not destructive, and not idempotent.

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?

Very short, but missing critical context. Concise but incomplete for a one-sentence description.

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?

No output schema and description doesn't mention return value or side effects. Agent lacks info on what the duplicate collection contains or what is returned.

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 covers 100% of parameters with description. Tool description adds no extra meaning to the parameter.

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?

Clearly states verb 'Duplicate' and resource 'entire collection'. Distinguishes from sibling `transkribus_coll_duplicate_doc`.

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. Many sibling collection tools exist (create, delete, list), but no when-not-to-use or alternative mentioned.

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