sheets_add_table

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

With no annotations, the description carries the full burden of disclosure. It fails to explain whether the table overwrites existing data, requires specific permissions, or returns any confirmation. It briefly mentions 'typed columns' and 'dropdown values' but does not elaborate on behavioral implications.

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, concise sentence with no superfluous words. It efficiently conveys the core purpose and key features.

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?

Given 5 parameters (all required), no output schema, and nested objects in 'columns', the description lacks completeness. It does not explain how to structure the columns array, what each column type entails, or what the tool returns after creation.

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%, so baseline is 3. The description adds minimal context beyond the schema: 'typed columns and optional dropdown values' rephrases what the schema enums already convey but does not explain parameter interactions, like how 'range' bounds the table or the uniqueness constraint on 'name'.

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 'Create a native Google Sheets table with typed columns and optional dropdown values', specifying the verb (Create), resource (native Google Sheets table), and key features. This distinguishes it from siblings like 'sheets_update_table' and 'sheets_delete_table'.

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 provides no guidance on when to use this tool versus alternatives, such as 'sheets_update_table'. It does not mention prerequisites (e.g., sheet existence) or conditions where this tool should be avoided (e.g., if the range is already occupied).

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