remove_query_parameter

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

With no annotations, the description must carry disclosure. It mentions a Raises condition but doesn't cover whether removal is permanent, whether the parameter must first exist, or any side effects. For a mutating operation this is thin.

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?

Single-sentence purpose then Args/Raises blocks. No fluff; the action sentence is front-loaded.

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?

Two required parameters, no output schema, no annotations. The description doesn't state what counts as a valid site_url or what 'remove' does to existing crawl data, and the Raises line lacks conditions beyond failure.

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 Args section just restates the parameter names with trivial glosses; with 0% schema coverage the description was expected to compensate with concrete formats or examples, and it doesn't.

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 identifies the action ('Remove') and resource ('a URL normalization parameter from a site'), making the core purpose unambiguous. It doesn't explicitly differentiate from the sibling enable_disable_query_parameter, but the verb 'remove' distinguishes it well enough in most contexts.

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 removal versus toggling via enable_disable_query_parameter, or what prerequisites exist (e.g., site must be added/verified). The usage context is only implied by the verb 'remove'.

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