create_workbook

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

With no annotations, the description carries full burden. It states the tool creates a new workbook but does not disclose side effects (e.g., whether it automatically saves, sets it as active, or what happens on duplicate names). The parameter list adds some context but behavioral traits are minimal.

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 extremely concise with the main action in the first sentence, followed by a clean list of parameters. No unnecessary words or repetition. Every sentence serves a purpose.

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 simplicity (4 params, all optional, output schema exists), the description covers creation intent and parameter details well. Minor missing context: no mention of what happens on duplicate workbook names or if the tool returns any identifier. Still, it is largely sufficient.

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 provides brief but helpful explanations for each parameter (e.g., locale: 'Locale code (e.g. en, de, es, fr)'). This adds meaning beyond the schema's type and default, aiding correct invocation.

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 'Create a new empty workbook', which is a specific verb and resource. This distinguishes it from sibling tools like load_workbook, save_workbook, and other mutation tools. The purpose is immediately understood.

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 is provided on when to use this tool versus alternatives like load_workbook. There is no mention of prerequisites, such as whether a workbook must be closed first, or if calling this multiple times creates separate workbooks. The description lacks explicit usage context.

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