keep_bottom_rows

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

The description discloses that the tool appends Table.LastN to the table's M query, indicating it adds a transformation step rather than overwriting. However, with no annotations, it omits any side effects, reversibility, or impact on existing query steps, limiting transparency. No contradiction with annotations.

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 extremely concise, with two short sentences that front-load the main action and add an implementation note. No redundant information or filler.

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 simple transformation, the description gives the core operation and implementation, but it lacks usage context and parameter clarifications. With no output schema or annotations, it is minimally complete but leaves gaps around edge cases and table identification.

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 50% (count and partitionName described), but the tool description adds no parameter detail beyond implying N corresponds to count. It does not explain the table, sessionId, or how partitionName interacts, failing to compensate for the undocumented parameters.

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 the tool keeps only the last N rows from a Power Query table, with a specific verb and resource. It distinguishes from sibling tools like keep_top_rows by specifying 'last N rows' and from remove_bottom_rows by the 'keep' action. The implementation detail 'Appends Table.LastN' reinforces the specific operation.

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?

No guidance is provided on when to use this tool versus alternatives such as keep_top_rows, keep_range_rows, or remove_bottom_rows. The description only defines what it does, not the context or decision criteria, leaving the agent without direction for tool selection.

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