create_sheet

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

No annotations are provided, so the description carries the full burden. It discloses the basic creation action and return type but does not mention authentication requirements, duplicate sheet name behavior, or whether existing spreadsheet content could be affected. These gaps leave the agent to infer side effects.

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 compact and front-loaded with the core purpose, followed by a clean Args/Returns structure. There is no fluff or redundant material.

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 three-string create operation, the description covers the inputs and the confirmation return value. It lacks details on conflict handling or authorization, but given the low complexity and existing output schema, the description is largely complete.

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%, so the description's one-line explanations for each parameter add essential meaning. It clarifies that user_google_email is the user's email, spreadsheet_id identifies the spreadsheet, and sheet_name is the new sheet's name, though it offers no format or source guidance.

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: 'Creates a new sheet within an existing spreadsheet.' This clearly distinguishes it from create_spreadsheet and other spreadsheet-related siblings. The scope is unambiguous.

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 'within an existing spreadsheet' provides clear context for when the tool applies, implicitly separating it from creating a new spreadsheet. However, it does not explicitly name alternatives or state when not to use it.

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