skip_rows

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

No annotations are present, so the description carries full burden. It reveals it 'Appends Table.Skip to the table's M query', indicating a mutation, but doesn't mention reversibility, permissions, or side effects on previous query steps.

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, front-loaded with the core purpose, no irrelevant details. The structure is efficient and easy to scan.

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?

As a mutation tool with no annotations and no output schema, it omits information about return values, error handling, and the exact effect on the table in the model. It also doesn't clarify the table parameter's format or partition behavior beyond the schema.

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 50% description coverage. The description clarifies that count is the N rows to drop, and table is implied as the target. However, sessionId and partitionName are not explained beyond the schema's default description for partitionName.

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 'drop the first N rows', using a specific verb and resource, and the reference to Table.Skip distinguishes it from siblings like remove_bottom_rows for bottom rows.

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 through 'drop the first N rows', but no explicit alternatives or when-not-to-use guidance is provided. It doesn't mention other row-removal tools like keep_top_rows.

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