bing_crawl_settings_get

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that the return is narrowed to a single value; it says nothing about permissions, whether the value can be absent, or what 'partial contract' implies about data completeness.

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 or redundancy. It is efficient, though the trailing 'partial contract' clause costs clarity rather than adding it.

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 structure needn't be explained, but the lone parameter is undocumented and there is no usage context for a tool embedded in a dense Bing/SEO toolset. The definition is too thin for the agent to invoke confidently.

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% and the sole required parameter, 'site', is never mentioned in the description. The description does not compensate for the undocumented parameter, so the agent gets no signal about what 'site' should contain.

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 verb and resource: return Bing's observed crawl-rate value. The word 'only' distinguishes it from broader crawl tools like bing_crawl_stats or bing_crawl_issues. However, the phrase 'from the partial contract' is unexplained jargon that muddies what the tool actually reads from.

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 guidance is given, and no alternative is named despite many adjacent siblings (bing_crawl_stats, bing_crawl_issues, bing_url_info). An agent must guess whether this narrow getter or a broader crawl tool is appropriate.

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