Create a Google Sheet

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

Annotations already indicate readOnlyHint=false and openWorldHint=true, so the write nature is known. The description adds the requirement of a Google Drive connection (one connection covers Drive, Sheets, Docs) and clarifies that rows are optional, which goes beyond the schema. No contradiction with annotations.

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?

Three sentences with no filler. The purpose is front-loaded, followed by usage details and a prerequisite. Every sentence contributes meaningful information for the agent.

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 tool with two optional parameters and no output schema, the description covers everything needed: purpose, row format, return value (id + URL), and a connection prerequisite. The examples help the agent understand common use cases. Nothing critical is missing.

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 100% with descriptions for both parameters. The description adds value by clarifying that rows are optional, providing examples of what rows might contain, and noting that the first row is treated as headers. This complements the schema without redundancy.

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 a specific verb and resource ('Create a new Google Spreadsheet in the user's Drive') and provides concrete examples (export a swipefile, ad list, performance report). It clearly differentiates from siblings like append_to_sheet and update_sheet by focusing on creation of a new 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?

The description gives clear context (creating a new sheet, optionally with rows) and includes a prerequisite (Google Drive connected). It does not explicitly name alternative tools or when not to use it, but the purpose is unambiguous enough that an agent can infer when to use it vs. modifying existing sheets.

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