paste_delimited_data

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

The description only mentions 'paste delimited text/HTML' but does not disclose side effects (e.g., overwriting cells, expanding sheet), authentication needs, or rate limits. With no annotations, the description carries full burden and fails to provide sufficient behavioral detail.

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, short sentence that is concise and front-loaded. However, it could be slightly expanded without losing conciseness to improve clarity.

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 the complexity (6 parameters, no schema descriptions, no output schema, many siblings), the description is far too minimal. It fails to explain return values, parsing behavior, or what happens when data doesn't match delimiters.

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 0% description coverage, so the description must compensate. It hints at 'data' and 'start_cell' but does not explain 'html', 'paste_type', or 'delimiter' beyond implicit context. The agent would need to infer parameter meanings.

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 it pastes delimited text/HTML starting at a single cell, which identifies the verb and resource. It distinguishes from siblings like write_range that write raw data, though it could be more precise about parsing behavior.

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?

No guidance on when to use this tool versus alternatives like 'text_to_columns' or 'write_range'. The description lacks any usage context or exclusion criteria.

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