sheets_create_spreadsheet

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

Annotations already indicate this is a write operation and not destructive. The description adds useful behavioral context beyond annotations: the new file is placed in the account's 'My Drive' root, and the return value is a JSON string containing spreadsheet_id, title, and url. No contradiction with annotations exists.

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 concise and front-loaded. The key action and optional capability are in the first sentence, followed by placement guidance and return format. There is no wasted text; every sentence earns its place.

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 create-spreadsheet tool, the description is complete: it states what is created, where it is created, how to handle the folder-location edge case, and what the return value contains. The annotations cover safety and idempotency, so no additional behavioral disclosure is needed.

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 already documents title and sheet_names well, so the description does not need to repeat parameter details. The description does reinforce that named tabs are optional ('optionally with named tabs') and mentions title in the return value, but it does not add substantial meaning beyond the 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 opens with a specific verb and resource: 'Create a new Google Sheets spreadsheet, optionally with named tabs.' This clearly distinguishes it from read/write/append/clear sheet tools and from drive file upload tools. It also mentions the optional named-tab capability, which matches the sheet_names parameter.

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 gives clear placement context: the file lands in 'My Drive' root, and if a specific folder is needed, a follow-up move should be used. It names an alternative approach, though it does not fully specify the exact sibling tool to call for the move. This is clear context but not a fully exhaustive when-to-use guide.

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