Workbooks Deploy Template To Folder

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so safety is largely covered. The description usefully discloses that this is a composite two-step operation (instantiate then optionally swap sources), which is beyond what annotations say, but it omits permissions, collision/overwrite behavior, and whether the swap is transactional.

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?

A single front-loaded sentence with no filler, leading with the primary action and appending the optional step. Efficient, though extremely terse for the amount of behavior being described.

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?

An output schema exists, so return values need not be explained, but this is an open-world composite mutation with 4 parameters at 0% schema coverage and no usage or failure guidance. The description leaves too much unspecified for an agent to call it confidently.

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 and largely does not. It maps loosely onto template_id and folder_id, but says nothing about the required 'name' parameter (naming/collision semantics) or the format and meaning of 'connection_mapping'.

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?

States a concrete verb+resource: 'instantiate a template into a folder' plus the optional source-swap step. This is clearly distinct from read/duplicate siblings, though it never names the closest alternative (workbooks_create_workbook_from_template) to sharpen the distinction.

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?

No guidance on when to pick this over workbooks_create_workbook_from_template or a create-then-elements_swap_template_sources sequence. The word 'optionally' hints at a conditional step but never states the condition or the alternative path.

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