set_basic_filter

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

With no annotations provided, the description discloses key behaviors: it can set or clear a filter, accepts a range (or whole sheet), and includes a dry_run option to preview changes without applying. This covers the main behavioral traits, though destructive effects or authorization needs are not mentioned.

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 concise: one sentence for purpose followed by a compact list of parameters. Every line adds value, and the main action is front-loaded. No superfluous content.

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?

Given the simplicity of the tool and absence of output schema, the description covers essential aspects: how to specify the sheet and range, the clear and dry_run flags. It could mention what happens on success or if filter already exists, but overall it is fairly complete for a mutation tool.

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 0%, so the description must fully explain parameters. It does so for all five: spreadsheet_id_or_url (URL or ID), sheet (name or gid), range (A1 or None for whole sheet), clear (remove filter), and dry_run (plan without changes). This adds substantial meaning beyond the raw 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's action: 'Set (or clear) the basic filter of a sheet.' It identifies the resource (sheet's basic filter) and the verb (set/clear), distinguishing it from sibling tools that deal with rows, columns, or sheets.

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 does not explicitly guide when to use this tool vs. alternatives. While the sibling tools are all different operations, there is no mention of when to use set_basic_filter over other filter-related tools (none exist in siblings), so implied usage is clear but no explicit context.

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