filter_data

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

The description mentions read-only SQL, indicating safe operation. Though no annotations are provided, it implies non-destructive behavior. Missing explicit statement about side effects or idempotency, but sufficient given the context.

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?

Two sentences, front-loaded with core purpose, then crucial usage restriction. No unnecessary words. Every sentence adds value.

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 no annotations, output schema, and 7 parameters, the description covers all needed context: what it does, constraints, and integration with sibling tools. Complete and actionable.

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?

Adds meaning beyond the schema by clarifying that filters are exact column=value mappings, and that SQL overrides filters. Provides an example. Schema coverage is high, but the description enhances understanding without redundancy.

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 purpose: to filter/aggregate rows of a structured resource using exact filters or read-only SQL. It specifies the resource type (DataStore-active) and differentiates from siblings by noting the prerequisite check via inspect_dataset.

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?

Explicitly states when to use (DataStore-active resources) and when not to (other resources, use get_dataset_data instead). Provides actionable guidance to verify has_datastore via inspect_dataset, and names specific alternatives.

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