mysql_index_suggestions

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

With no annotations, the description discloses generation of SQL, inclusion of composite variant and EXPLAIN guidance, and the limitation of not verifying existing indexes. It does not detail permissions or side effects, but for a generation tool this is sufficient.

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 sentences, no wasted words. The first sentence conveys the core functionality and inclusions, while the second provides usage context and a limitation.

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 simple input schema and no output schema, the description adequately covers what the tool does, when to use it, and a key caveat. It is complete for the tool's complexity.

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 descriptions for both parameters. The description adds minimal value beyond the schema, as it does not elaborate on parameter constraints or format. Baseline 3 is appropriate.

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 it 'Generates the exact ALTER TABLE ADD INDEX SQL for a MySQL table column', including composite variant and EXPLAIN guidance. This is specific and distinguishes from sibling tools targeting other databases like Postgres or MongoDB.

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?

It explicitly says 'Call this when the analyzer flags a missing MySQL index or full table scan finding' and notes it does not verify existing indexes. However, it does not mention alternative tools or when not to use it.

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