copy_dataframe

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

With no annotations provided, the description carries the full burden. It reveals that the copy is 'deep', implying the source remains unchanged, and that it creates a new name. It doesn't discuss overwrite behavior or error handling, but for a simple copy operation, this is reasonably transparent.

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 two sentences, front-loaded with the purpose, followed by a concise usage tip. Every word serves a purpose; there is no redundancy or filler.

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 two-parameter, simple copy tool, the description covers the operation, the new-name behavior, and the optimal usage timing. The output schema exists, so return value details are unnecessary. Minor details like whether existing names get overwritten are not critical for such a straightforward tool.

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 0%, but the parameter names `source_name` and `new_name` are self-explanatory. The description reinforces the purpose of `new_name` with 'under a new name' and clarifies the operation is a deep copy. While it doesn't explicitly define each parameter, the contexts provided by the description makes the semantics clear.

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 clearly states the tool's function with a specific verb and resource: 'Create a deep copy of a dataframe under a new name.' It distinguishes this tool from all sibling manipulation tools by focusing on copying, and no other sibling performs this exact action.

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 gives explicit when-to-use guidance: 'Use BEFORE any destructive operation (dropping, filtering, encoding) if you may need the original data later.' It does not mention when not to use it or name alternatives, but given there are no alternative copy tools among siblings, this is sufficient context.

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