analyze_missing_indexes

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

No annotations provided, but description covers input requirements and output structure. Notes automatic uppercasing of table name. No mention of side effects or auth, but read-only nature is implied.

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?

Very concise: one sentence describing purpose, then parameter explanations. No wasted words, all information is essential.

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?

Despite no output schema, description specifies return format (array of objects with columns, has_index, index name or null, unique). Covers three parameters adequately. Complete for tool 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 0%, but description fully explains each parameter: database as key from list_databases, table from list_objects with uppercasing, filterColumns as optional comma-separated list. Adds significant meaning beyond schema.

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?

Clear verb and resource: 'report which columns are covered by an active index'. Distinguishes from sibling tools like describe_table or get_execution_plan by focusing specifically on index coverage analysis.

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?

Provides clear usage context: requires a database and table, optional filterColumns for WHERE/JOIN columns. No explicit when-not-to-use or alternatives, but the purpose is sufficiently specific.

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