Suggest a MySQL index

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that (it only generates SQL text). It adds real context beyond the annotations: the output includes a composite variant plus EXPLAIN verification guidance, and it explicitly disclaims existence checking.

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?

Three short sentences, front-loaded with what is produced, then when to call it, then the caveat. No filler or restatement of the title.

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?

There is no output schema, but the description compensates by describing the deliverable (ALTER TABLE statement, composite variant, EXPLAIN guidance), which is exactly what an agent needs to know before invoking it. Nothing material is missing for a two-parameter read-only generator.

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 coverage is 100% with two well-described required parameters (table, column), so the schema already carries the parameter semantics. The description's phrase 'for a MySQL table column' merely restates that pairing and adds no format or constraint detail, making 3 the correct baseline.

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 and artifact: generates the exact ALTER TABLE ADD INDEX SQL for a MySQL table column. The MySQL qualifier cleanly separates it from the sibling index tools (postgres_index_suggestions, suggest_mongo_index, suggest_gsi) without needing to open any schema.

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?

Gives an explicit trigger: 'Call this when the analyzer flags a missing MySQL index or full table scan finding.' It also states one boundary condition (does not check for an existing index), but it never names an alternative tool for non-MySQL engines, leaving that routing to the name alone.

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