sheets_create

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

With no annotations, the description carries the full burden. It discloses the optional sheet_names behavior (creating custom tabs) but does not mention side effects like file creation in Drive, required write permissions, or any constraints. It adds some value beyond the raw action but lacks thorough behavioral context.

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, tightly worded sentence that front-loads the action ('Create a new Google Spreadsheet') and includes the optional modifier. Every word earns its place with no redundancy.

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, two parameters, and the presence of an output schema (which covers return values), the description covers the core action and parameter semantics adequately. It does not need to explain return values because the output schema exists. Minor gaps like permissions are not critical for a straightforward create tool.

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 coverage is 0%, so the description must compensate. It explicitly ties 'title' to the spreadsheet name and explains that 'sheet_names' are optional custom sheet/tab names, adding meaning beyond the bare parameter titles. This is sufficient for the simple two-parameter schema.

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 the tool creates a new Google Spreadsheet, with a specific verb ('Create') and resource ('Google Spreadsheet'). It also mentions optional custom sheet/tab names, distinguishing it from sibling tools like sheets_add_sheet which operate on existing spreadsheets.

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 description implies usage (when you need a new spreadsheet), but does not explicitly contrast with alternatives like sheets_add_sheet or docs_create. No when-to-use or exclusionary guidance is provided, leaving the agent to infer from the name and context.

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