Duplicate Document

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

No annotations are provided, so the description must carry full behavioral disclosure. It only mentions copying markdown content and setting title/parent, but fails to disclose permissions required, side effects (e.g., comments, attachments), rate limits, or how the new doc is returned.

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?

Two sentences, front-loaded with the core action. Every word adds value, no redundancy.

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 mutation tool with no annotations and no output schema, the description is too brief. It does not explain return values, required permissions, or whether the operation is reversible. Given the complexity of duplication (permissions, attachments), the description is incomplete.

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 75% (workspaceId lacks description). Description adds context by stating title defaults to '<original title> (copy)' and parentDocId positions in sidebar, which goes beyond schema. However, workspaceId is not addressed, and its purpose is left implicit.

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 clearly states it clones a document by copying markdown content into a new doc, optionally setting title and parent. This specifies the verb (clone/duplicate) and resource (document), distinguishing it from creation tools like 'create_doc' or 'create_doc_from_template'.

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?

Description implies usage for duplicating an existing document but does not explicitly state when to use versus alternatives like 'create_doc_from_markdown' or 'batch_create_docs'. No guidance on prerequisites or exclusions.

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