yuque_copy_repo

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

No annotations are provided, so the description carries the full behavioral burden. It discloses one useful trait ('creates TOC dirs and copies') but omits permissions/auth requirements, overwrite or conflict behavior on the target repo, idempotency, and whether the operation is synchronous or long-running.

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 front-loaded sentences covering action and input shape, with no padding. The trailing pointer to an external markdown file is terse but not self-contained.

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 3-parameter mutation tool with no annotations and no output schema, the description leaves key gaps: return value, failure modes, source-vs-target semantics, and the undefined 'cleaned documents' contract that the agent must satisfy. It leans on an out-of-band reference file rather than being self-sufficient.

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 100%, so the baseline is 3. The description adds only marginal value by restating the documents shape as (title/body/format/paths) and flagging that documents must be 'cleaned,' without defining what cleaning entails.

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?

States a specific verb and resource ('Batch copy documents to another repo') plus the side effect of creating TOC dirs. The 'batch' qualifier implicitly separates it from the singular yuque_copy_doc, though no sibling is named outright.

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 explicit when-to-use guidance and no named alternatives (e.g., yuque_copy_doc for a single doc, yuque_import_file for file ingestion). The only hint is 'Agent provides cleaned documents array,' which describes input prep rather than tool selection.

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