bing_fetched_url_details

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: the empty_response label semantics, the warning that empty results are silence rather than a clean bill of health, and the handling of untrusted fields. These are non-obvious operational facts an agent must know before reporting results.

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?

Front-loaded purpose, then usage, then failure-mode and safety caveats. Every sentence adds distinct value with no repetition of the schema or annotations.

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?

With no output schema, the description supplies the missing output semantics: the empty_response label and how to interpret it, plus the untrusted-data rule. Combined with the annotations, an agent has everything needed to call and interpret this tool correctly.

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 parameters, so the description carries the full burden. 'One URL it has crawled' loosely implies the meaning of url, but site_url is never mentioned and neither parameter's expected format or relationship is explained. This is a real gap for a required two-parameter tool.

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 ('Read Bing's fetch detail for one URL it has crawled') with explicit singular scope. The description immediately distinguishes it from the sibling bing_fetched_urls, so an agent can select correctly 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?

Gives an explicit trigger ('when the user asks what happened the last time Bing fetched a specific URL') and an explicit exclusion with a named alternative ('Do not use this for the list of recent fetches; call bing_fetched_urls'). Nothing about selection is left to inference.

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