maintenance_vacuum

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

Given no annotations, the description discloses the synchronous nature, potential up-to-60-second delay, and the effect of reclaiming disk space. It does not mention potential locking or concurrency effects, but overall transparent.

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 well-structured with a clear lead sentence and follow-up details. It is moderately concise; every sentence adds value, though some minor redundancy could be trimmed.

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?

The description covers purpose, usage, and performance, but does not mention the return value or output format (e.g., what the tool returns after vacuum or dry run). Since no output schema is provided, this gap reduces completeness.

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?

The schema already describes the dry_run parameter, but the description adds practical context: 'Use this to preview how large the database is before committing to a full vacuum.' This adds value beyond the 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 clearly states 'Reclaim disk space after large purge operations by running VACUUM on the local SQLite database.' It specifies a specific verb and resource, and distinguishes itself from sibling tools like deep_storage_purge and backup_database.

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?

The description explicitly advises calling after deep_storage_purge and explains why (SQLite doesn't reclaim pages automatically). It also notes remote backend behavior. However, it lacks explicit when-not-to-use or alternative tools.

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