bing get geo file

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description contributes real behavioral context beyond that: the link is returned as data and is not downloaded, and the Location IDs are Microsoft-specific and incompatible with Google's. That last point is a meaningful gotcha the agent would otherwise miss.

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?

Three short sentences with no waste. The core action leads, followed by the ID caveat and the return behavior, so the most important facts are front-loaded.

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 an output schema present, the description need not explain return structure, and it still clarifies that the link comes back as data rather than being downloaded. Combined with the annotation coverage and full schema descriptions, an agent has essentially everything needed to invoke this 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?

Only one parameter, and schema coverage is 100% with a detailed accountId description (numeric ID, not the eight-character account number). The description adds nothing about the parameter, so the schema does all the work; baseline 3 is appropriate when coverage is complete.

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: retrieving the current Microsoft/Bing geographic targeting file link. That is clearly distinct from the other sibling tools (campaigns, ads, keywords, reports). It stops short of naming a sibling it contrasts with, so it lands at 4 rather than 5.

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 a concrete usage rule: use the returned Location IDs and never reuse Google location IDs. That tells the agent the context in which this tool's output matters. It doesn't explicitly route away from a sibling such as bing_get_targeting, so no exclusions are stated.

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