Looker.Query.Run

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it provides very little. It does not state that this is a read-only operation, does not mention permissions, query cost, row limits, or whether filters are combined with AND/OR—context that matters for a query execution 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?

The single sentence is front-loaded and free of filler. It is arguably too terse for a tool with four required parameters including a nested filters object, but the sentence itself is efficiently constructed.

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 four required parameters, nested filter objects, zero schema descriptions, and no annotations, the description is not complete enough. The output schema reduces the need to explain return values, but the input-side semantics and behavioral context are still largely absent.

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 schema provides only parameter names and types. The description merely repeats 'fields + filters' and names model/view without explaining expected formats, filter syntax, field naming conventions, or what happens when filters are empty despite being required.

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: run an inline model/view query with fields and filters. It is clear enough to distinguish from list/get operations, but it does not explicitly differentiate itself from the sibling tool looker.look.run, which handles saved Looks.

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?

There is no guidance on when to use this tool versus looker.look.run or other Looker siblings. The word 'inline' hints at ad hoc querying rather than saved Looks, but that implication is not made explicit and no exclusions or prerequisites are stated.

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