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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds meaningful context: it submits URLs, expends daily quota, and benefits ChatGPT/Copilot. No contradiction with annotations; the quota disclosure is extra behavioral detail beyond what structured fields provide.

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 action and purpose, followed by the quota warning and usage condition. No superfluous words; every clause earns its place.

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 simple tool with two fully documented parameters, annotations covering safety, and no output schema, the description is sufficient. It covers when to use, what it does, and a key constraint (quota). Minor omissions like post-submission behavior are not critical for correct invocation.

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 100% for both parameters (site and urls), so the structured schema already documents their meaning. The description adds no additional parameter-level insight beyond what the schema states; it implicitly references quota usage but the schema already notes that each URL uses one unit. Baseline 3 applies since the schema carries the load.

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 states a specific action ('submit new or updated URLs to Bing') and the resource (Bing), with a clear goal (crawled fast). It also distinguishes from sibling inspection/analysis tools by focusing on submission, and the condition 'Only call when the user asks to submit' reinforces a unique purpose.

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 explicitly states when to use it ('Only call when the user asks to submit') and gives a practical constraint ('Uses your daily Bing quota') implying scarce usage. It does not explicitly contrast with alternatives, but the condition and quota note provide sufficient context for an agent to decide when to invoke it.

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