✓ 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?

Without annotations, the description carries the transparency burden. It discloses the tool reclaims space and defragments, implying a write operation with a space cost. However, it omits details like database locking, duration, reversibility, or whether it's safe to run concurrently.

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 sentence, concise and front-loaded with 'MAINTENANCE.' It wastes no words, though it duplicates the title. It could be more structured (e.g., listing prerequisites separately), but it remains efficient.

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 tool is a maintenance operation with one optional parameter and no output schema, the description is too sparse. It explains the 'what' and a space requirement but lacks context on effects (e.g., does it lock?), usage patterns, or how it relates to siblings like 'backup_database' or 'database_info.'

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 has 0% description coverage for its single parameter 'database_name.' The description does not mention the parameter, its purpose, default behavior (if omitted applies to current?), or valid values. The description adds no 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?

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 provides a key prerequisite: 'Requires free space equal to database size.' This helps an agent decide when to use it. However, it offers no guidance on when not to use this tool or mention of alternatives among the 20+ siblings.

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