copy_wiki_node

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

States 'deep-copy' and 'duplicated' indicating non-destructive copy. No annotations, so description carries burden. Could disclose permissions or limits but adequate.

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?

Single concise sentence with 'Official API' prefix. No unnecessary text; every word adds value.

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, but operation is simple. Covers source, destination, and optional title. Could mention that parent tokens refer to wiki nodes, but context is 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 covers all 5 parameters with descriptions (100% coverage). Description adds no extra param info beyond 'deep-copy' context. Baseline 3 is appropriate.

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?

Clear verb 'deep-copy' and resource 'Wiki node', with destination scope. Distinguishes from move_wiki_node (move vs copy) and create_wiki_node (copy vs create) among siblings.

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?

Implies use when a duplicate is needed. Contrasts with move implicitly. Lacks explicit 'when not to use' but sufficient for typical scenarios.

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