remove_query_parameter

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

With no annotations, the description carries the full burden. It explicitly discloses that 'Cleans up the empty <QueryParameters/> block when removing the last one', which is a specific and useful behavioral trait beyond basic deletion. This adds value and context about side effects.

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 short sentences that front-load the main purpose and add a key behavioral detail. No wasted words. Highly efficient and scannable.

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 three required parameters with zero schema coverage and no output schema, the description is far too minimal. It lacks explanations of parameter roles, return behavior, error conditions, or prerequisites (e.g., does the parameter need to exist?). Completeness is insufficient for reliable tool 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 0%, yet the description provides zero information about any of the three required parameters (name, path, dataset_name). The agent must rely solely on parameter names, which are insufficient for correct invocation. This is a critical gap.

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 action ('Remove a query parameter from a dataset') and adds a specific behavioral detail about cleanup. However, it does not distinguish this tool from sibling tools like 'remove_parameter' which likely removes a different kind of parameter. The purpose is clear but lacks sibling differentiation.

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 is provided on when to use this tool versus alternatives (e.g., update_query_parameter or remove_parameter). The description only states what the tool does without any conditional or contextual advice. There is no explicit when/when-not or alternative naming.

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