hosting_repairDatabaseV1

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

Without annotations, the description carries the full burden. It mentions 'asynchronously,' which is a key behavioral trait, but does not disclose potential destructiveness, repair duration, or how to check status. Minimal but adds the async characteristic.

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?

Two short sentences with the main action upfront and no extraneous text. Every sentence adds value.

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 when to use and a parameter constraint, but lacks information on return values or how to monitor the async repair. Given no output schema, this gap could hinder an agent from proceeding correctly.

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 100%, and the description merely restates the schema's note about the 'name' parameter needing to be the full name from list databases. It adds no new insight beyond what the schema already provides.

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 states 'Repairs corrupted database tables asynchronously,' using a specific verb and resource. It clearly distinguishes from sibling tools like list, create, delete, and change-password operations.

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?

Explicitly states 'Use when database errors, crashes, or corruption are reported,' providing clear usage context. Also notes that the database name must come from the list databases endpoint, hinting at prerequisite tool use.

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