add_query_parameter

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

No annotations are provided, so the description should carry the full burden. It mentions that a BingWebmasterError is raised if the parameter cannot be added, but does not disclose whether parameters are overwritten, if idempotency applies, or any other side effects of the addition.

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 extremely concise with two clear sentences, an Args section, and a Raises note. Every sentence serves a purpose without fluff.

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 zero annotations, three required parameters with poor schema coverage, and an output schema that exists but is not described, the description fails to provide enough context for correct invocation. The 'self' parameter is ignored, and the return behavior is omitted.

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 only adds minimal meaning for site_url and query_parameter, repeating their names. The required 'self' parameter is completely undocumented, leaving the agent uninformed about its purpose.

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 (add) and the resource (URL normalization parameter for a site). It distinguishes from sibling tools like remove_query_parameter and enable_disable_query_parameter by implying addition as a distinct operation.

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 versus alternatives such as enable_disable_query_parameter or remove_query_parameter. The description lacks context for typical use cases or prerequisites.

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