postgres_index_suggestions

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

No annotations provided, so description fully bears the burden. It discloses generation of both full and partial index SQL, an ANALYZE reminder, and that it does not verify existing indexes. Could mention that it does not execute the SQL, but the word 'generates' implies only SQL output.

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 front-loaded sentences: first delivers primary function, second provides usage context and an important caveat. Every sentence earns its place with zero waste.

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 tool with 2 simple string parameters and no output schema, the description is nearly complete. It covers purpose, when to use, and a key limitation. Could briefly note the output is SQL text, but otherwise adequate.

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 covers both parameters with descriptions (100% coverage). The description does not add extra parameter-level details beyond what the schema provides, so baseline score of 3 is appropriate.

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?

Description clearly states it generates exact CREATE INDEX CONCURRENTLY SQL for a PostgreSQL table column, including a partial index variant and ANALYZE reminder. It distinguishes from sibling tools like mysql_index_suggestions or suggest_gsi by specifying PostgreSQL and the exact SQL generation.

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?

Explicitly recommends calling when the analyzer flags a missing index or when writing a query filtering on an unindexed column. Lacks an explicit 'when not to use' statement, but the provided use cases are clear and directional.

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