set_auto_filter

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

No annotations are provided, but the description discloses key behaviors: it adds filter UI only (not selecting values), can remove filters, range scope, and one filter per sheet. This covers the essential behavioral traits for a mutation tool.

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?

Three sentences, all front-loaded with purpose. Each sentence adds unique value: function, parameter guidance, and behavioral note. No waste.

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 tool with no output schema, the description fully covers purpose, parameter usage, and behavioral nuances. Sufficient for an agent to select and invoke correctly.

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 coverage is 0%, so description compensates by explaining 'range' (header+data or whole used range) and 'remove' (clear filter). 'Sheet' and 'session_id' are not elaborated, but session_id is standard context. Two of four parameters get meaningful explanation beyond schema.

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 adds Excel's filter dropdowns to a data range, with the clarifying note 'one filter per sheet'. This is specific and distinguishes it from sibling tools like add_data_validation or format_as_table.

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 usage guidance: range should cover header row plus data, omit for whole used range, and remove=true clears the filter. It also clarifies that filter selection happens in Excel, not via this tool. Lacks explicit when-not-to-use, but context is sufficient.

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