✓ MAINTENANCE: Optimize storage by reclaiming space and defragmenting. Requires free space equal to database size.

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

No annotations are provided, so the description must disclose behavioral traits. It mentions reclaiming space and defragmenting, which implies a write operation, and states the free space requirement. However, it omits details like locking behavior, duration, or failure conditions.

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 two sentences, but the first sentence repeats the title verbatim. The second adds a requirement. Could be more concise by removing redundancy and front-loading the critical space requirement.

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 the maintenance nature of this tool, the description lacks information on side effects (e.g., database unavailability), return values, or scenarios where vacuuming is inappropriate. With no output schema and no annotations, more contextual details are needed.

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%, and the description does not explain the optional parameter 'database_name' beyond its name in the schema. It lacks details on what happens if omitted (e.g., defaults to current database) or formatting constraints.

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?

Tautological: description restates name/title.

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 provides a key precondition: 'Requires free space equal to database size.' This helps the agent decide when to use it. However, it does not mention when not to use it or suggest alternatives.

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