gsheets_spreadsheets_create

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

Annotations already declare a non-read-only, open-world mutation. The description adds meaningful context beyond that: creation only establishes structure and metadata, and cell content must be written in a separate call. It does not mention required permissions or quota behavior, keeping it at a 4 rather than 5.

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 sentences, zero filler, front-loaded with the primary action and followed by the runtime detail and the next-step tool references. Every clause carries information.

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 create tool with no output schema, the description covers the action and the follow-up write path, which is the essential mental model. It omits what the call returns (e.g. the created spreadsheet ID needed by downstream calls), a minor gap given the otherwise complete guidance.

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 nested `spreadsheet` object and its fields are already well documented. The description names title, locale, time zone and sheets but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 new spreadsheet') and enumerates what can be configured (title, locale, time zone, starting sheets). It also routes the agent to the sibling write tools, so it is distinguishable from the values_update/append operations at a glance.

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?

Gives clear context for the create-then-populate workflow by naming `spreadsheets_values_update` and `spreadsheets_values_append` as the follow-up path for writing cell values. It does not state explicit exclusions or preconditions (e.g. auth scopes), so it falls short of a full 5.

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