gws.sheets.create

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds valuable behavioral detail: optional seeded tab, return of ID and URL, ownership by account, and the guarantee of not modifying existing content. This goes beyond the structured metadata without contradicting it.

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 somewhat redundant: 'Create a new Google Spreadsheet' and 'Creates a new, empty document owned by the account' repeat similar information, as do the two mentions of returning ID/URL. While front-loaded with the primary action, the repetition means not 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 create tool with no output schema, the description adequately covers inputs, behavior (seeding, non-modification), and return values (ID and URL). It does not mention required scopes or permission topics, but annotations hint at open-world behavior. Overall fairly complete for its complexity.

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 has 100% coverage for all three parameters. The description enhances initial_values by explaining its array-of-arrays shape and that it seeds starting at A1, which the schema description only calls 'cell grid'. This adds meaningful format context 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 clearly states the verb 'Create' and specific resource 'new Google Spreadsheet'. It distinguishes from siblings by specifying it never modifies existing content, differentiating it from write_range, and the 'Spreadsheet' scope differentiates it from docs.create.

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 phrase 'It never modifies existing content' provides clear context for when not to use this tool (i.e., when modifying existing sheets). It also references write_range for the shape of initial_values, hinting at an alternative. However, it does not explicitly name alternatives or state 'use write_range for modifications'.

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