copy_workspace

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

No annotations are provided, so the description must disclose behavior. It mentions the suffix for uniqueness but omits whether the new workspace is created (though schema hints), whether the source is affected, whether existing connectors in the target are overwritten, and what happens on failure. This leaves significant behavioral ambiguity.

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 sentence, front-loaded with the verb, and every phrase contributes meaning. No wasted words.

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?

The tool performs a complex bulk operation with potential side effects (creating workspace, renaming IDs, copying all connectors), and there is no output schema or annotations. The one-line description does not address return values, creation behavior, failure modes, or effect on source workspace, making it insufficiently complete.

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%, and the schema already describes all three parameters, including the suffix's purpose. The description adds little beyond restating the schema, so baseline 3 applies.

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 uses specific verb 'Copy' and clearly identifies the resource (all connectors) and transformation (suffix added to connector IDs). It distinguishes from sibling copy_connector which presumably copies a single connector.

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 clearly states the action and context (copy all connectors from source to new workspace), making it obvious when to use. However, it does not explicitly mention alternatives like copy_connector for single-connector copies, so no exclusions are stated.

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