wordpress_advanced_wp_db_repair

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

No annotations are provided, so the description carries full burden. While it mentions 'REPAIR TABLE', it fails to disclose critical behavioral traits: whether the operation locks tables, requires downtime, is potentially destructive to data, or requires specific database privileges. No information about output format is provided despite no output schema existing.

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 extremely concise with only two sentences and no fluff. The '[UNIFIED]' prefix appears to be metadata leakage but doesn't significantly impact clarity. The front-loading is adequate (action first, mechanism second).

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?

Database repair operations are high-risk administrative tasks, yet the description provides minimal safety context. Given zero schema descriptions, no output schema, no annotations, and the destructive potential of table repair operations, the description is dangerously incomplete. It should warn about risks and explain failure modes.

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?

With 0% schema description coverage, the description must compensate significantly but fails to do so. It implies the default behavior (repair all tables when `tables` is null) but doesn't explain what the `site` parameter expects (URL, ID, slug?), nor what format the `tables` array items should be (strings, objects?). The schema's `items: {}` provides no type information, leaving the agent guessing.

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 the tool repairs corrupted database tables using the REPAIR TABLE command. However, it claims to run on 'all WordPress tables' which conflicts slightly with the optional `tables` parameter that allows specific table selection, and it doesn't differentiate from similar maintenance tools like `wordpress_wp_db_check` or `wordpress_wp_db_optimize`.

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?

No guidance provided on when to use this versus alternatives (like `check` or `optimize`), no prerequisites mentioned (e.g., backups, maintenance mode), and no warnings about when NOT to use it. The agent receives no signal about appropriate usage contexts.

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