Workbooks Create Workbook From Template

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the mechanics are partly covered. The description adds one capability trait (chart/table visuals only via template), but says nothing about required permissions, what folder placement means, or side effects of creating the new workbook.

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?

Two short sentences, front-loaded with the action and then the differentiator. The second sentence is somewhat promotional ('real visuals'), but it carries a genuine capability distinction, so little is wasted.

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 a creation tool with three undocumented parameters, no permission/prerequisite note, and no pointer to template-source siblings leaves the agent guessing how to invoke it correctly.

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% across three parameters, including two required ones (template_id, folder_id), so the description carries the full documentation burden and does not meet it. Only template_id is faintly implied by 'from a template'; name and folder_id are never explained.

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 specific verb and resource ('Create a workbook from a template') and the 'from a template' qualifier distinguishes it from workbooks_create_workbook and workbooks_duplicate_workbook. It does not name those siblings explicitly, so an agent must infer the distinction rather than read it.

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 claim that this is 'the only programmatic way to get charts/tables' gives a reason to choose this tool over a blank-workbook creation, which is useful implied guidance. However, there is no explicit when-to-use/when-not, no mention that a template_id must first come from workbooks_list_templates or workbooks_get_template, and no named alternatives.

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