postgres_index_suggestions

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

With no annotations, the description carries the full burden. It discloses key behaviors: generates exact SQL, includes partial index and ANALYZE reminder, and explicitly states it does not verify existing indexes. It does not detail execution context, but the scope is clear.

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 sentences, front-loaded with the core purpose, then usage guidance and a caveat. Every sentence earns its place; no wasted words.

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 simple parameter set and no output schema, the description fully covers what the tool does, when to use it, and an important limitation (no duplicate checking). It is complete for the intended purpose.

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%, so baseline is 3. The description adds context ('PostgreSQL table column') but does not provide additional semantic detail beyond schema descriptions. The parameters are self-explanatory.

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 states the tool's purpose: generating exact CREATE INDEX CONCURRENTLY SQL for a PostgreSQL table column, including variants and reminders. It explicitly names the resource (PostgreSQL table column) and the action (generates SQL), distinguishing it from sibling tools like mysql_index_suggestions.

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 provides explicit when-to-use guidance: when the analyzer flags a missing index or when writing a filter query on an unindexed column. It does not mention alternatives but the context is clear. A slight improvement would be to directly contrast with siblings, but it is still effective.

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