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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description's contribution is clarifying that all=true is a full wipe rather than a filtered delete, but that scope is also stated in the schema description for 'all', so the added value is modest.

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 compact sentence that front-loads the primary mode (keyed deletion) and appends the bulk mode with its use case. Nothing is wasted, though the embedded example duplicates the schema.

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 four-parameter destructive tool with no output schema, the description covers both deletion modes adequately. It omits what the tool returns (e.g. count of deleted rows), whether missing keys cause errors, and the changelog 'note' behavior, leaving some gaps for a mutation tool.

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 all four parameters (dataset, keys, all, note) are already documented in the schema, including the same key example the description repeats. Baseline 3 is appropriate since the description adds no format or constraint detail beyond the schema.

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?

States a specific verb (deletes) and resource (rows from a dataset), with two clear modes: keyed deletion and full wipe. An agent can distinguish it from delete_dataset and upsert_rows, though it never names those siblings explicitly.

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 parenthetical 'use before re-loading a dataset from scratch' gives one concrete when-to-use scenario for all=true. There is no guidance on when to prefer keyed deletion, when to use upsert_rows instead, or any exclusion such as what happens if a key does not exist.

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