Looker.Look.Run

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

With no annotations, the description carries the full behavioral burden, but it only says that result_format defaults to json. It does not disclose permission requirements, whether running a look consumes query resources, or what happens on invalid ids. The only behavioral detail given merely restates the schema default.

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 efficient sentence with the action and resource front-loaded. The parenthetical about result_format is useful but partially redundant with the schema default, keeping it from a 5.

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 an execution tool with two parameters, no annotations, and an output schema that covers returns, the description still omits result-format alternatives, permission requirements, and differentiation from looker.query.run. An agent would need to inspect the schema and guess at behavior before invoking it.

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 explain both parameters. It mentions look_id and result_format but gives no valid values for result_format beyond the default and no format or provenance expectations for look_id. This is only marginally more informative than the bare 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 states a specific verb and resource: run a saved look identified by its id. That is clearly distinguishable from looker.looks.list (listing) and reasonably from looker.query.run (ad-hoc queries). It does not explicitly contrast itself with looker.query.run, so it stays below a 5.

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.query.run or looker.looks.list, and no prerequisites such as needing an existing look id or appropriate permissions. The usage is only implied by the name and the phrase 'saved look by id'.

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