clear_rows

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

The description discloses the destructive nature (delete all rows) and adds context beyond annotations: keeping schema intact and requiring AUTARIO_API_KEY. It aligns with annotations (destructiveHint=true) and provides extra value.

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 two sentences with no wasted words. It starts with the action, states the effect, gives a use case, and mentions a requirement. Perfectly concise.

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 tool with one parameter, no output schema, and simple behavior, the description is complete. It explains what happens (delete rows, keep schema), why use it (refresh data), and a requirement (API key). No gaps.

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?

The single parameter 'dataset_id' has a clear description in the schema ('The UUID of the dataset to clear all rows from'), and schema coverage is 100%. The description does not add additional meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 all rows from a dataset while keeping the schema and columns intact,' using a specific verb and resource. It distinguishes from siblings like 'delete_dataset' and 'write_rows' by emphasizing that only rows are removed, not the structure.

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 a clear use case: 'Useful for refreshing data before re-importing.' It implies when to use but does not explicitly state when not to use or mention alternatives, though the sibling context makes the distinction clear.

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