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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-web profile is covered by structured data. The description adds nothing beyond that – no note on result volume, pagination behavior, or filtering limits – so it contributes no behavioral context of its own.

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?

The description is a single three-word phrase, so it is maximally concise and front-loaded, but it is under-specified rather than efficiently informative. It earns its brevity at the cost of usefulness.

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 5-parameter search tool, the rich input schema (100% coverage) and the presence of an output schema cover most mechanical needs, so the description need not explain return values. However, with numerous competing image/search siblings, the description should at least route the agent, and it does not.

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%, with every parameter (Page, Count, Query, Country, Language) documented in the schema itself, including defaults and clamping ranges. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 'Bing image search' essentially restates the tool name (bing_images) with no additional specificity about scope, result type, or what distinguishes it from siblings like bing_search, bing_news, bing_videos, brave_images, or duckduckgo_image. An agent learns only that it is a Bing image search, which the name already conveyed.

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?

There is no guidance on when to use this tool versus the many other image/search siblings, no mention of prerequisites or constraints, and no exclusions. The intended usage (searching for images) is only weakly implied by the phrase 'image search'.

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