tc_copy_folder

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

Beyond annotations, the description discloses that the operation walks the tree, recreates folders, copies files one by one, can be slow, and may be truncated by max_items. It also mentions the requires write flag and returns an errors field, providing substantial insight into behavior.

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?

The description is somewhat lengthy but well-structured: core action, then caveats, then args, then return value. Each sentence provides valuable information without redundancy, though it could be tightened by moving the args list to a more compact format.

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 the tool's complexity and the provided output schema, the description covers all necessary context: operation mechanics, performance caveats, configuration requirement, parameter semantics, and return value structure. It is complete enough for an agent to decide when to use it and what to expect.

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 0%, so the description fully compensates by explaining each parameter. It clarifies target_parent_folder_id as 'Folder that will contain the copy,' new_name defaults to the source name, and max_items as a safety cap—meaning beyond the schema.

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?

The description states 'Copy a folder and everything inside it to another location' with a specific verb and resource, clearly distinguishing it from sibling tools like tc_copy_file. The title 'Copy folder (recursive)' reinforces the scope.

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?

The description explains when to use this tool by noting that Trimble Connect lacks a server-side copy endpoint, so a manual walk is needed. It warns about slowness for large trees and mentions the max_items cap and the TC_ENABLE_WRITE requirement, but does not explicitly name alternative tools.

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