create_spreadsheet

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

With no annotations, the description carries the full burden for behavioral disclosure. It explains what is created, how optional sheet_names behave (default single sheet), and what the return value contains. It does not mention authentication prerequisites or that the operation is a permanent write, but it is reasonably transparent 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 structured as a docstring with a one-line summary followed by concise, relevant parameter and return explanations. Every sentence adds value and there is no padding or 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?

The description covers the tool's purpose, all parameters, default behavior, and return type. It does not address how it relates to sibling tools like create_sheet or mention authentication steps, but it is otherwise complete for invoking the tool successfully.

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 description coverage is 0%, but the description compensates fully. It explains each parameter, marks required fields, specifies the type and role of sheet_names, and clarifies the default behavior. This goes well beyond what the bare schema provides.

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', a specific verb+resource that clearly distinguishes it from siblings like create_sheet (which adds a sheet to an existing spreadsheet) and create_drive_file. The name itself is also descriptive.

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 case by detailing parameters and return behavior, but it does not explicitly say when to prefer this over create_sheet or other alternatives. There is no exclusion guidance or mention of prerequisites, leaving some ambiguity for an agent deciding between similar tools.

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