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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds real behavioral value beyond that by disclosing the return fields (matched_name, confidence as a 0-1 score) and the reliability caveat that ambiguous inputs may match the wrong POI. It does not mention rate limits, coordinate reference system, or failure behavior when nothing matches.

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?

Two sentences, front-loaded with purpose and followed by return values plus an ambiguity-handling instruction; no filler. Density is high but each clause carries actionable information, though the second sentence packs return fields and user-confirmation policy together.

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?

There is no output schema, so the description must explain return values — and it does, naming matched_name and confidence with their semantics, plus how to handle low confidence. Missing only minor details such as what happens on zero matches or which coordinate system is returned, which are low-risk for this simple tool.

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?

There is only one parameter, and the schema already documents it at 100% coverage as '地名/地标'. The description restates essentially the same meaning without adding format, language, or disambiguation hints for the input itself. Baseline 3 applies when the schema carries the parameter semantics.

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: convert a place name/landmark into lat/lng coordinates, and ties it to a concrete downstream use in find_nearby. An agent can immediately distinguish this lookup tool from siblings like find_nearby or nearby_attractions.

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 clear workflow context (geocode first so the result can be fed to find_nearby) and prescribes an action for the ambiguous-name case: check matched_name and, if unsure, relay both values to the user. It stops short of explicit when-not-to-use conditions or alternatives for already-known coordinates.

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