Delete rows

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds genuine extra context: a 100-row cap per call and the fact that it returns the number deleted. It does not dig into partial-failure behavior or what happens with invalid ids, keeping it at a solid but not rich 3.

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?

Two short sentences with the operational rule and the return value front-loaded; nothing wasted beyond the lowercase 'delete rows' fragment that merely echoes the title.

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 destructive 3-parameter tool with full schema coverage and annotations carrying the safety profile, the description covers the batch cap and return shape, leaving little an agent needs to know. Edge cases (nonexistent ids, partial deletes) are omitted but are minor at this complexity.

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 already explains ds_/row_ prefixes, comma-separated syntax, 1-based positions, and the 100-row combined limit. The description restates the same combination rule without adding format nuance, which is baseline 3.

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 ('Remove rows' from a dataset) and enumerates the two ways to identify rows, which distinguishes it from siblings like delete_dataset, update_dataset_row, or list_dataset_rows. It does not explicitly name a sibling it might be confused with, so 4 rather than 5.

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?

Usage is implied by the 'ids and/or positions' framing and the note that one is required, but there is no explicit when-to-use versus when-not-to-use guidance or reference to alternatives. An agent can infer the purpose from the model, but routing is left to the reader.

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