bing_url_submit

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

With no annotations, the description carries the full behavioral burden, and it discloses one genuinely useful non-obvious fact: submission does not guarantee or assert indexation. However, it omits quota/rate-limit behavior (a sibling, bing_url_submission_quota, implies quota exists), whether site ownership/verification is required, and what happens on rejection.

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?

A single front-loaded sentence with no filler; the scope qualifier and the indexation caveat are both packed in without wasted words.

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?

An output schema exists so return values need not be described, but for a submission (write) tool with zero annotation coverage and 0% parameter documentation, the definition leaves too much open: no auth/verification requirement, no quota expectation, and undefined parameters.

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% for both required parameters, so the description must compensate. 'Same-origin URL' and 'site' together imply the URL must belong to the site's origin, which is a meaningful constraint, but neither parameter is defined (format, whether site is a domain vs. a verified property, whether URL must be absolute).

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?

States a specific verb and resource ('Submit one ... URL to Bing') and the 'one' framing distinguishes it from the batch siblings like bing_urls_submit_batch and submit_batch. It also pins a scope constraint ('same-origin'). It stops short of naming the alternative tools, but an agent can still tell what it does.

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 when-to-use or when-not-to-use guidance, and none of the competing submission paths (bing_urls_submit_batch, indexnow_submit, submit_sitemap, bing_feed_submit) are referenced. The 'without claiming indexation' caveat hints at expectations but does not route the agent between tools.

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