Recommend TurboQuant maintenance

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

Annotations provide readOnlyHint=true, and the description is consistent, adding details like 'returns empty list when extension not installed' and 'feeds audit_database category'. This adds useful behavioral context beyond the 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?

The description is concise, well-structured, and front-loaded with the main action. It efficiently lists rules and edge cases without unnecessary 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 complexity and presence of an output schema, the description covers all important aspects: what it does, rules surfaced, suggested actions, edge case for missing extension, and relation to audit_database. No gaps.

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?

The only parameter 'database' is fully described in the input schema (100% coverage). The description does not add any additional meaning or context about the parameter beyond what the schema already provides.

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 verb 'walk every pg_turboquant index and emit advisor findings', specifies the resource (pg_turboquant indexes), and lists specific rules surfaced. It distinguishes from siblings like recommend_indexes which likely deal with regular indexes.

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 when TurboQuant extension is present (returns empty list if not installed) but does not explicitly state when to use this tool vs alternatives like recommend_turboquant_query_knobs. No exclusions or direct comparisons to siblings.

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