submit_urls

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

With no annotations, the description carries the full burden and does genuinely useful work: the 500-URL cap, the daily quota constraint, and the conditional behavior keyed on the INDEXNOW_KEY environment variable, including which engines IndexNow reaches. It stops short of stating what happens when the quota is exhausted, whether submission guarantees indexing, or what authentication is required.

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 sentences, front-loaded with the primary action and the cap, followed by the conditional secondary behavior. No filler, no restatement of the tool name.

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?

For a 2-required-parameter mutation tool with no annotations and no output schema, the behavioral side is well covered (quota, cap, dual submission), but the description explains nothing about the return value or confirmation semantics and leaves 'site_url' entirely undefined. An agent could call it, but with avoidable uncertainty about the required site identifier.

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 coverage is 0%, so the description needs to compensate. It does bound the 'urls' array at 500, which is real semantic value beyond the bare array-of-string schema, but it says nothing about 'site_url' — no format guidance (scheme, trailing slash, whether it must match the URLs' host) for a required parameter.

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 — submitting up to 500 URLs to Bing's URL Submission API, with a conditional IndexNow fan-out. The URL-level granularity implicitly and clearly separates it from the sibling submit_sitemap, so an agent can pick between them without opening either schema.

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 phrase 'crawl up to 500 URLs now' and the mention of a daily quota imply the use case (pushing fresh/updated URLs for immediate indexing), but the description never states when NOT to use it or names submit_sitemap as the alternative for bulk sitemap-based submission. Usage is inferable rather than explicit.

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