repair_mysql_database

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

No annotations are supplied, so the description carries the full burden and does almost nothing with it. For a repair operation it says nothing about data-loss risk, whether the database should be backed up first, required privileges, downtime, or whether the action is reversible.

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?

One short sentence, front-loaded with the verb and resource, with no filler. Brevity is efficient, though it borders on under-specification given the operation's risk profile.

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?

With no annotations and no output schema, the description is the only behavioral source, and it omits the safety and outcome information an agent needs before invoking a destructive-feeling repair. It also leaves the operation's scope unclear — whole database versus individual tables.

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?

There is a single parameter and the schema documents it at 100% coverage ('Database name to repair'), so the schema already carries its meaning. The description adds no extra detail such as accepted naming formats or table-scoping options, so baseline 3 applies.

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?

States a specific verb ('Repair') and resource ('damaged or corrupted tables in a database'), making the operation distinguishable from neighbours like list_mysql_databases or delete_mysql_database. It does not explicitly differentiate itself from the sibling check_mysql_database, which is the closest related tool.

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 phrase 'damaged or corrupted tables' implies the triggering condition for use, so usage is inferable. However, it never says when NOT to use it, never mentions checking a database first with check_mysql_database, and never mentions restore_database_backup as an alternative recovery route.

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