Recommend TurboQuant query knobs

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

The description adds behavioral context beyond the readOnlyHint annotation, detailing two operation modes and the specific output parameters. It includes a prerequisite (pg_turboquant). No contradictions 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?

The description is concise, with two clear sentences and a bullet list. It front-loads the main purpose and efficiently conveys the two modes and output knobs.

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?

The description adequately covers the tool's functionality, modes, and output, and references related tools. It compensates for low schema coverage by explaining the parameter groupings. However, it lacks details on parameter constraints or ranges, and the output schema is only implied but not explicitly stated (though the output schema exists).

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 description adds meaning to parameters by explaining the two modes and optional fields (final_limit, filter_selectivity). The database parameter is well-documented. However, it does not explain the purpose or typical values of candidate_limit and final_limit, nor what index_schema and index_name represent beyond their names. Given low schema coverage (17%), more parameter explanation would be beneficial.

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 it runs tq_recommended_query_knobs as a per-query knob advisor. It distinguishes two modes (plain and index-aware) and lists the returned knobs, making the purpose specific and distinct from sibling tools like recommend_hnsw_ef_search.

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 explains when to use each mode: plain with just candidate_limit (and optional final_limit), index-aware with index_schema and index_name. It also instructs to pass returned knobs to related tools. However, it does not explicitly state when not to use this tool or provide alternatives.

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