delete_rows

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

With no annotations, the description discloses two important behaviors: filter requirement and dry-run default. However, it does not explain other aspects like overwrite, output, or the destructive nature, leaving gaps.

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?

A single sentence with no wasted words, but it may be too brief given the tool's complexity (8 parameters). It is efficient but borderline under-specified.

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?

With 8 parameters, no schema descriptions, no annotations, and 13 siblings, the description fails to cover essential context like path, match structure, output, or return value. Very incomplete.

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 0%, and the description only mentions 'filtered rows' and 'dry-run' but does not explain most parameters (path, match as Filter array, options, overwrite, etc.). Significant lack of parameter detail.

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 'Delete filtered rows', which is a specific action on a specific resource, distinguishing it from sibling tools like update_rows or append_rows. It also adds key constraints: requires non-empty filter and defaults to dry-run.

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 use when deleting rows matching a filter, but does not explicitly say when not to use it or mention alternatives like update_rows. The dry-run default hints at cautious usage, but no direct guidance.

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