naver_reverse_geocode

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it states the conversion function, it doesn't describe important behavioral aspects: what format the address is returned in, whether there are rate limits, what happens with invalid coordinates, whether authentication is required, or what service provider is used (Naver). For a tool with no annotation coverage, this is insufficient.

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 extremely concise - a single sentence that directly states the tool's function. There's no wasted language or unnecessary elaboration. However, it could benefit from being slightly more informative while maintaining efficiency.

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?

Given the tool has no annotations and no output schema, the description is incomplete. It doesn't explain what format the address is returned in, what happens with invalid coordinates, whether there are limitations or prerequisites, or how this differs from sibling tools. For a coordinate-to-address conversion tool with no structured output documentation, the description should provide more context.

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?

The schema description coverage is 100%, with both parameters (lat, lng) clearly documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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 clearly states the tool's purpose: converting latitude/longitude coordinates to an address. It uses specific verbs ('변환합니다' - converts) and resources ('위도/경도 좌표' - latitude/longitude coordinates, '주소' - address). However, it doesn't explicitly distinguish this reverse geocoding function from its sibling 'naver_geocode' (which likely does forward geocoding).

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tools (naver_directions, naver_geocode, naver_search_places) or explain when reverse geocoding is appropriate versus forward geocoding or place search. There's no context about prerequisites or limitations.

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