health_vacuum

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

No annotations are provided, so description must disclose behavioral traits. It states the tool scans and identifies objects but does not indicate whether it is read-only, requires permissions, or has side effects. The phrase 'for cleanup' could mislead agents into thinking deletion occurs, but it only identifies objects. Missing clear disclosure of non-destructive nature.

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 efficiently convey purpose and scope. Front-loaded with the main action, followed by specifics. No unnecessary words or redundant information.

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?

Description covers core functionality and parameter meaning, but lacks usage guidance and behavioral transparency. Given an output schema exists, return values are explained elsewhere, so text is adequate but incomplete without disclosure of read-only nature or tips for effective use.

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 100% with a single parameter 'scope' described. The tool description largely repeats the schema's explanation (scan explores vs. content), adding no new semantic value beyond what the schema already provides.

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?

Description clearly states the tool identifies unused or orphaned LookML objects for cleanup, listing specific types (explores, unreferenced views, zero-view Looks/dashboards). It distinguishes itself from health_analyze and health_pulse by focusing on cleanup rather than general health analysis.

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?

Description implies use for cleanup but does not explicitly state when to use this tool versus alternatives like health_analyze or health_pulse. No exclusion criteria or usage scenarios are provided.

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