mysql_legacy_list_indexes

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

Because annotations are absent, the description is the sole source of behavioral information. It explicitly labels the tool as read-only and reveals the exact SQL syntax, which is useful. However, it does not disclose authorization requirements, error behavior, or the type of result rows returned, leaving a partial outlook.

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?

The description is a single sentence that front-loads the action and the underlying SQL, ending with a useful safety note. There is no filler or repetition.

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?

For a simple tool with only two required parameters and no output schema, the description covers the basic invocation and reveals the SQL command. It doesn't describe the exact result structure of SHOW INDEX or error conditions, but it is enough for the agent to select and call it 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?

The schema has zero description coverage, so the description must compensate. It clearly maps the parameters to the placeholders in the SHOW INDEX statement (<database> and <table>), giving useful meaning beyond the raw schema types. It doesn't describe how the parameters behave for special cases, but it suffices for basic usage.

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 a specific verb ('Lists') and resource ('indexes from a table') and gives the exact SQL command ('SHOW INDEX FROM <database>.<table>'), making it clearly distinguishable from sibling tools like list_tables or describe_table.

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?

No guidance is provided on when to use this tool instead of alternatives. It offers no mention of when the SQL or when to prefer describe_table or show_create_table. The read-only flag implies safe use but not actionable direction.

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