Create spreadsheet

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the action and optional tabs, without mentioning side effects like persisting a file in Drive, authentication requirements, or what the create operation returns. This is a meaningful gap for a mutation tool.

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 a single short sentence with the core verb and noun front-loaded and no filler words. It communicates the essential action and the one optional behavior efficiently.

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 tool with no annotations and no output schema, the description should clarify return values or side effects. It only states the action, leaving the agent unaware of what the tool returns (e.g., a spreadsheet ID/URL) or how the account parameter affects execution. A simple phrase about return value would make it complete.

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 100%, so the schema already documents all three parameters. The description adds minimal value by noting that sheet tabs are optional ('pre-made sheet tabs'), which echoes the schema's non-required status. No further parameter semantics are needed beyond this baseline.

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 uses the specific verb 'Create' with the resource 'spreadsheet' and an optional modifier about pre-made sheet tabs. It clearly distinguishes itself from sibling read/write/append tools and other Google resource creates by naming the exact resource type.

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 phrase 'Create a new spreadsheet' implies the tool is for creating rather than editing an existing spreadsheet, giving some usage context. However, it does not explicitly mention alternatives or when-not-to-use conditions, so the guidance is only implied.

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