sheets_create_spreadsheet

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states 'Create a new Google spreadsheet' without mentioning authentication, rate limits, what happens if the title already exists, or any other side effects. This is insufficient for a creation 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 sentence: 'Create a new Google spreadsheet.' It is concise and front-loaded with the core action. However, it could include a bit more context without becoming verbose, such as what it returns or a note about the sheetTitle parameter.

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 simple tool with no output schema and no annotations, the description should explain what the tool returns (e.g., the new spreadsheet's ID or URL). It also omits any constraints like title length limits or default behavior. This leaves the agent uncertain about the output and edge cases.

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?

The input schema has 100% coverage, with descriptions for both 'title' and 'sheetTitle'. The description adds no additional meaning beyond these schema descriptions. According to guidelines, baseline is 3 when coverage is high, and no extra value is provided.

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 Google spreadsheet,' specifying the verb (create), resource (spreadsheet), and platform (Google). This distinguishes it from sibling tools like sheets_add_sheet or sheets_append_values, 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 its use for creating a new spreadsheet but provides no explicit guidance on when to use versus alternatives, such as 'use this to start a new spreadsheet, not to add sheets to an existing one.' No when-not-to-use or prerequisite information is given.

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