filter_data_advanced

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

With no annotations, the description must disclose side effects. It mentions optional output_sheet writing and a returns dict, but it does not clarify whether the original file is modified, the exact behavior when output_sheet is null, or what 'summary' means. This is adequate but has gaps.

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 well-structured with a clear one-line purpose, an Args section, and a Returns section. Every line adds relevant information, and there is no fluff or repetition.

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 return behavior is underspecified ('Filtered rows or summary') and the optional write path is not fully explained. Given the tool's complexity (6 parameters, nested conditions) and absence of annotations and output schema, the description should provide more detail about what is returned in different scenarios.

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 description provides meaningful semantics for all six parameters, explaining the structure of conditions, the purpose of logic, output_sheet's optional write behavior, and header_row indexing. This fully compensates for the schema's lack of top-level parameter descriptions (0% coverage).

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 states a specific verb and resource: 'Filter rows using multiple conditions combined with AND/OR logic.' This clearly distinguishes it from sibling tools like sort_data or aggregate_data, and the mention of multiple conditions and logic makes the advanced filtering scope obvious.

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 clear context for when to use the tool (filtering rows with multiple conditions and AND/OR combination). However, it does not explicitly name alternatives or state when not to use it, so it falls short of a perfect score.

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