sheets_add_table

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description does not need to repeat those safety traits. However, it adds no additional behavioral context, such as potential side effects, permissions required, or behavior on duplicate names. It is not misleading, but it is minimal.

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 single, front-loaded sentence that conveys the core purpose without any filler. Every word contributes to understanding the tool's function.

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 operation with full schema documentation and non-destructive annotations, the description provides sufficient context. It covers the essential action and distinguishing features, and the schema handles parameter specifics. The lack of output schema or explicit return value explanation is a minor gap, but not critical for basic usage.

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 100%, so the schema fully documents all five parameters. The description adds no extra parameter details beyond mentioning 'typed columns and optional dropdown values,' which is already reflected in the columnType and dropdownValues fields. Baseline 3 is appropriate.

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 resource 'native Google Sheets table' with specific attributes (typed columns, optional dropdown values). It effectively distinguishes this tool from sibling tools like sheets_update_table, sheets_delete_table, and sheets_get_tables.

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 usage for creating a Google Sheets table, but it does not explicitly state when to use this tool over alternatives or provide exclusions. The purpose is clear, but there is no direct comparison to related operations like updating or deleting tables.

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