mysql_index_suggestions

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

Discloses that it does not verify index existence. No annotations provided, so description carries burden. Could mention if it modifies anything (it doesn't; generates SQL only) but overall good.

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 succinct sentences covering purpose, usage trigger, and caveat. No redundant information.

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 simple parameters and no output schema, description covers purpose, trigger, and a behavioral caveat. Could mention output format (like SQL string) but not essential.

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. Description does not add extra meaning beyond schema. 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?

Clearly states it generates ALTER TABLE ADD INDEX SQL for a MySQL column, with composite variant and EXPLAIN guidance. Specific verb and resource, distinct from sibling tools targeting other databases.

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 says 'Call this when the analyzer flags a missing MySQL index or full table scan finding.' Provides clear context. Does not explicitly mention alternatives, but implied by tool name and sibling list.

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