map_poi

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

No annotations are present, and the description does not disclose any behavioral traits such as side effects, limitations, error handling, or data sources. The only additional info is pricing and API endpoint, which are cost-related, not behavioral.

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 very short and front-loads the purpose, but it includes unnecessary details about pricing and API endpoint. While concise, it lacks structured information that would aid agent comprehension.

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 no output schema, no annotations, and a terse description, the agent lacks essential context about expected results, error conditions, or usage constraints like search radius. This is inadequate for a 3-parameter 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?

Input schema covers all three parameters with descriptions (lat, lng, type) at 100% coverage. The description adds no extra semantics beyond the schema, which is adequate but not enhanced. No enum values or further explanation for the 'type' parameter.

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 '周边POI搜索' clearly indicates a nearby POI search functionality. While it doesn't explicitly differentiate from sibling map tools like map_geocode or map_route, the purpose is clear and specific enough for an AI agent to understand.

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 guidance is provided on when to use this tool versus other map-related siblings. The description lacks context for appropriate usage scenarios, leaving the agent without decision support.

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