bing_suggest

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

Discloses locale defaults (country=us, lang=en-us), source (public Bing endpoint), and trimming to requested count. With no annotations, the description adequately conveys read-only behavior and constraints, though it could mention no side effects explicitly.

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 efficient sentences: first states purpose, second describes output, third covers defaults and source. No unnecessary words, well-structured for quick parsing.

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?

Covers purpose, behavior, and parameters adequately for a simple suggestion tool. Lacks description of return format, which is mitigated by the schema's 100% coverage and the implicit nature of suggestions. Output schema absence is noted but not critical.

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 100%, so baseline is 3. Description adds context about defaults for country and lang and explains trimming for count, which is helpful but not extensive. Does not compensate for missing output schema.

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?

Clearly states 'Suggest Bing search queries' and 'Returns Bing autosuggest query completions for a query prefix', identifying the verb and resource. Distinguishes from sibling suggest tools by specifying Bing as the source and from other Bing tools by focusing on query completion.

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?

Description implies usage for generating autocomplete suggestions, but does not explicitly state when not to use or compare to alternatives like bing_search. However, the purpose is clear enough for selecting this tool over siblings.

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