analyze_query_indexes

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

Annotations already mark as readOnly. The description adds a constraint of 10 queries but does not disclose other behavioral traits such as performance impact or that it uses DTA or LLM methods (only in parameter enum). Consistent with annotations.

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?

Single sentence of 12 words, front-loaded with verb and resource. 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 the presence of an output schema (not shown) and the tool's focused purpose, the description is fairly complete. However, it could mention the output format or that recommendations are advisory, but not required.

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% and each parameter has a description. The description adds a global constraint ('up to 10') not in the schema, but does not enhance individual parameter 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?

The description clearly specifies the verb 'analyze', the resource 'SQL queries', and the outcome 'recommend optimal indexes'. It distinguishes from siblings like 'explain_query' (single query plan) and 'analyze_workload_indexes' (workload-level).

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?

The description implies usage for index recommendation on up to 10 queries, but does not explicitly state when to use this tool versus siblings like 'analyze_workload_indexes' or 'get_top_queries'. No alternatives or when-not-to-use guidance is provided.

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