run_vacuum

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

No annotations exist, so description fully carries burden. Discloses irreversibility, exclusive lock, prior stats capture, and audit trail. Well beyond minimal expectations.

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?

Front-loaded with risk indicator and clear summary. Parameter descriptions are structured as a list, but could be slightly more concise (e.g., inline instead of bullet style).

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?

Covers all key behavioral and parameter details. Lacks explicit mention of return value or side effects on other transactions, but overall sufficient given sibling context and tool complexity.

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%, but description provides detailed explanations for each parameter (table, full, analyze, dry_run, target), adding essential context beyond schema names and types.

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?

Clearly states the tool performs VACUUM on a table with optional FULL and ANALYZE. Uses specific verb and resource, and the [WRITE] tag distinguishes it from read-only siblings.

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?

Provides important constraints (no undo, exclusive lock for FULL) and dry_run preview. Implicitly differentiates from analysis tools but does not explicitly list when to use vs. siblings.

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