add_filter_view

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

With no annotations, the description carries full burden but only states 'add a filter view'. It fails to disclose side effects (e.g., overwriting, requirements, return values) or the nature of the operation (non-destructive? requires permissions?).

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 a single sentence with no wasted words, but it is too terse and lacks important details. Conciseness should not come at the cost of usefulness.

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 5 complex parameters, no output schema, no annotations, and no parameter descriptions, the description is severely incomplete. It does not help an agent understand how to invoke the tool 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%, and the description adds no explanation for any of the 5 parameters (range, title, sort_specs, filter_specs, spreadsheet_id). The agent has no guidance on how to construct complex parameters like filter_specs or sort_specs.

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 specifies the verb 'add', the resource 'filter view', and the scope 'over an A1 range', which distinguishes it from siblings like update_filter_view and delete_filter_view. However, it does not differentiate from set_basic_filter or explain what a filter view is.

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 like set_basic_filter or update_filter_view. The description does not mention any prerequisites or context for using a filter view.

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