update_query_parameters

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

With no annotations, the description must disclose behavioral traits. It only states the purpose but does not explain default behavior (merging vs replacing), side effects (e.g., removing parameters not mentioned), or authorization requirements. The input schema hints at replace/remove options, but the description lacks an overview.

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 a single sentence, which is concise but lacks structure. It could benefit from brief notes on key parameters (e.g., replaceParameters) or a summary of behavior. It is minimally adequate.

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 tool has complex parameters (merge vs replace, remove) and no output schema or annotations, the description is insufficient. It does not explain how these operations work together or what the expected outcome is, which is critical for safe usage.

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 the baseline is 3. The description adds no extra meaning beyond the schema; it merely restates the tool's purpose. The schema descriptions are detailed, so no points deducted.

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 uses a clear verb-resource pair: 'Update a query's saved parameter definitions'. It explicitly specifies the resource (query's saved parameters) and distinguishes from sibling tools like 'update_query' (which updates the query itself) and 'get_query_parameters' (read-only).

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?

No guidance on when to use this tool vs alternatives like 'update_query' or 'create_query'. There is no mention of prerequisites, frequency, or when merging vs replacing parameters is appropriate.

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