remove_query_parameter

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

The description indicates the tool is destructive (removing a parameter) and can raise an error, but it does not disclose side effects, authentication needs, or any safety information. With no annotations, the burden was higher but unfulfilled.

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 short and front-loaded with the primary action. However, the Args section could be better integrated into a narrative, and the Raises clause is minimal. The structure is acceptable but not optimal.

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 covers the basic action and two parameters, but misses 'self' and provides no output or behavioral context. Although an output schema exists, the description still feels incomplete for a 3-parameter tool.

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%. The description only repeats parameter names for 'site_url' and 'query_parameter' without adding meaning beyond the schema. The 'self' parameter is entirely omitted, leaving it unexplained.

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') and resource ('URL normalization parameter') and context ('from a site'), effectively distinguishing this tool from siblings like 'add_query_parameter' and 'enable_disable_query_parameter'.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or complementary tools. It lacks any explicit when-to-use or when-not-to-use context.

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