update_query_parameter

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

Provides useful behavioral context about @-prefix normalization and legacy name addressing, but does not disclose potential side effects, required authorizations, or behavior on non-existent parameters. Given no annotations, the description partially compensates but remains incomplete.

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?

Very concise with two sentences and no wasted words. Could be slightly improved by front-loading the most critical information, but structure is 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?

With 5 parameters, no output schema, and no annotations, the description fails to cover the parameter semantics or return behavior. The normalization note is helpful but does not sufficiently complete the tool's context for safe and correct invocation.

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 0%, so the description must explain parameters. It only clarifies the 'name' parameter's addressing and 'value_expression' role. Other critical parameters (path, dataset_name, force_at_prefix) are not explained, leaving the agent without guidance.

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?

Clearly states the verb 'Change' and resource 'the value expression of an existing query parameter'. Distinguishes from sibling tools like add_query_parameter, remove_query_parameter, and rename_parameter by specifying exactly what is updated.

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?

Implies usage for updating value expressions of existing parameters, but lacks explicit guidance on when to use this versus alternatives like remove+add or other set_parameter_* tools. No exclusions or prerequisites mentioned.

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