create_spreadsheet

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

No annotations are provided, so the description carries full burden. It describes the creation process but omits the behavior of the dry_run parameter (default true), which affects whether the spreadsheet is actually created. This is a critical behavioral gap.

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 well-structured with Args and Returns sections, making it easy to scan. It is concise with no unnecessary sentences, though it could be slightly more compact.

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 presence of an output schema (not shown) and 4 parameters, the description covers creation purpose, required params, optional sheet_names, and return value. However, the omission of dry_run and lack of error or permission info leave gaps.

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 explains user_google_email, title, and sheet_names, adding meaning beyond the schema. However, it fails to mention the dry_run parameter, which is present in the schema with a default of true, reducing completeness.

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 starts with 'Creates a new Google Spreadsheet,' which is a clear verb+resource pair. It effectively distinguishes from siblings like create_doc, create_sheet, and create_drive_file.

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?

No guidance on when to use this tool versus alternatives (e.g., create_sheet, create_drive_file). There is no mention of prerequisites, such as having Google Drive access or the need for user authentication.

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