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

Annotations declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false, so the safety profile is carried by structured fields. The description adds nothing about caching caveats (no_cache), quota/rate limits, auth needs, or that destructiveHint=true despite a read-looking search. Big gap for a tool whose annotations flag it as destructive.

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 efficient trigger sentence with no padding, front-loaded with the resource keywords. It is appropriately sized, though it is one long enumeration rather than structured guidance.

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 8 parameters, 100% schema coverage, no output schema, and no-annotations gap on behavior, the description should at least explain pagination and place_id lookup interplay or when not to use it. It is far too thin for a tool of this complexity.

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%, so the burden is already met by the schema. The description only echoes parameter names (place_id, pagination) without adding syntax or format details, so it is baseline 3.

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?

Description states a specific resource (Bing Maps results, place search, locations, place_id, paginated data) with a clear trigger verb, so an agent knows roughly what it fetches. It does not differentiate from the sibling google_maps, which the same style of query would also serve.

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?

The trigger clause '当用户需要查询...时触发' implies usage context, but gives no explicit when-to-use versus google_maps/google_local, and no exclusions. Usage is only implied, which is the minimum viable level.

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