create_spreadsheet

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

With no annotations, the description carries full burden. It discloses side effects (creates new file owned by user in My Drive root) and auth requirement (spreadsheets OAuth scope). It doesn't describe return value, but output schema exists. Minor omission of whether creation is reversible or conflicts.

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 plus side effect/alternatives, no wasted words. Front-loaded with purpose, then important context. Highly efficient.

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 output schema exists, the description sufficiently covers purpose, side effects, alternatives, and auth. It doesn't explain return values but that's covered by schema. Lacks mention of what happens if file with same title exists, which could be added for completeness.

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?

Input schema has 100% coverage with descriptions for all 3 parameters. The description adds no additional detail beyond schema, so baseline 3 is appropriate.

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 it creates a new empty Google Spreadsheet in My Drive with specific verb and resource. It distinguishes from siblings like create_sheet (adds tabs to existing), create_drive_file, and import_to_google_doc, providing precise differentiation.

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?

It provides clear context for when to use this tool vs alternatives (create_sheet for tabs, create_drive_file/import_to_google_doc for .xlsx uploads) and mentions required OAuth scope. However, it doesn't explicitly exclude all inappropriate uses, such as editing existing files.

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