analyze_workload_indexes

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

readOnlyHint=true already tells the agent this is a safe read, so the description needed to add context such as where the workload statistics come from, runtime cost, or required privileges. It adds only the vague notion of 'frequently executed queries' and says nothing about how expensive the analysis is or what it depends on.

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?

A single efficient sentence with the action front-loaded and zero filler. It is short, though arguably too short given the gaps elsewhere.

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?

An output schema exists, so return values need not be explained. Still, for a workload-analysis tool the description omits the preconditions and cost of the analysis, leaving the agent without enough to judge when the call is appropriate.

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 description coverage is 100%, so both connection and max_index_size_mb are documented in the schema, setting the baseline at 3. The description adds no meaning about how max_index_size_mb constrains the recommendations, so it earns no premium.

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?

States a specific verb and resource: analyze frequently executed queries and recommend optimal indexes. However, it does not distinguish itself from the close sibling analyze_query_indexes (single-query analysis) or from get_top_queries, so an agent must infer the workload-vs-single-query split from the name alone.

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 phrase 'frequently executed queries' implies the workload-wide use case, but there is no explicit statement of when to pick this over analyze_query_indexes or get_top_queries, nor any prerequisites (e.g. query statistics needing to be enabled). Usage is only inferable.

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