worksheet_transfer

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

With annotations providing only readOnlyHint=false, the description adds meaningful behavioral context by warning that operations are 'expensive (many file opens) and destructive' and advising to document conflict resolution strategies. However, it does not detail specific destructive side effects, file locking, or overwrite 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 well-structured with clear sections (Args, Returns, Notes) and a concise opening summary. The parameter list is long but necessary given 18 parameters, and each line communicates grouping information. No redundant filler sentences are present.

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 (18 parameters, four distinct actions) and zero schema coverage, the description provides a broad overview but leaves gaps. It does not fully specify per-action workflows, expected return formats beyond 'str or dict', or how conflict_strategy behaves. The output schema exists but is not detailed in the description, so more context would be beneficial.

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 must compensate. It groups parameters by action (e.g., source_files/output_file/conflict_strategy for merge_workbooks) and explains which params apply to which operation. However, it lacks deeper semantics like allowed values for conflict_strategy, exact format for source_range, or behavior of copy_values/copy_styles.

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 that the tool performs cross-sheet and cross-workbook copy/merge/stack operations, and enumerates four specific actions (copy_range_across, copy_sheet_across, merge_workbooks, stack_sheets). It lacks an explicit distinction from sibling tools like copy_range or merge_datasets, but the action list provides concrete purpose.

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 offers no explicit guidance on when to use this tool versus alternatives such as copy_range or merge_datasets. It only notes that operations can be expensive and destructive, which is a warning rather than usage direction. There is no mention of preferred scenarios or exclusions.

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