create_spreadsheet

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

No annotations exist, so the description carries the burden. It clearly states the creation action and the return payload, but does not disclose permissions, potential side effects beyond creation, or behavior when title already exists. The 'new' keyword implies a fresh resource, but no details on authentication or rate limits.

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 compact docstring with a one-sentence summary, an Args list, and a Returns line. No redundant phrases or filler, achieving a good front-loaded structure.

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 creation tool with two parameters and an output schema, the description covers inputs and outputs adequately. However, it does not provide context about how sheet_names interacts with the default sheet, nor does it mention any prerequisites or alternatives, leaving a slight gap given the large sibling set.

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?

Both parameters are explained in the Args section: title is described as 'The title for the new spreadsheet' and sheet_names as 'Comma-separated list of sheet names (optional),' fully compensating for the 0% schema description coverage.

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 states 'Create a new Google Spreadsheet' with a specific verb and resource, clearly distinguishing from sibling create_sheet which adds a sheet to an existing spreadsheet.

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 explicit guidance on when to use this tool vs alternatives, though the name implies creating a new file. The description does not mention create_sheet as an alternative for adding sheets to an existing spreadsheet, leaving the differentiation implied.

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