remove_blank_rows

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

With no annotations provided, the description carries full burden. It discloses the exact predicate (every field blank) and that it appends a step to the M query, but it omits side effects such as reversibility, permissions, impact on query folding, or how existing steps are affected.

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 long, front-loaded with the main action, and contains no redundant information. Every word earns its place.

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?

The description is adequate for a simple transformation, explaining the operation and its implementation. However, the lack of parameter info, no annotations, and no output schema create noticeable gaps, making it not fully complete.

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 only 33% (only partitionName is described), and the tool description does not mention any of the parameters (table, sessionId, partitionName). It fails to compensate for the low schema coverage, leaving required parameters unexplained.

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 explicitly states 'drop rows where every field is blank (empty or null)', providing a specific verb and resource. It also differentiates from sibling tools by specifying the all-fields condition and the Table.SelectRows step.

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 usage for Power Query tables through its title and the phrase 'Appends Table.SelectRows', but it does not explicitly state when to use this tool versus alternatives such as remove_duplicates or filter_rows, nor does it mention exclusions.

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