get_offi_rent

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

No annotations are provided, so the description must disclose behavioral traits. It only says '조회' (inquiry), implying read-only, but omits pagination behavior, response format, and any rate limits. The presence of pageNo and numOfRows parameters is not mentioned, leaving the agent unaware of how to handle paged results.

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, front-loaded phrase that efficiently communicates the core purpose and key inputs. It contains no fluff, though it is slightly too terse to serve as a full description.

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 and no annotations, the description provides minimal context. It does not explain what the response contains, how to handle pagination, or any defaults. Given the moderate complexity of four parameters, this is insufficient for an agent to invoke the tool reliably.

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 covers only the two required parameters; the pagination parameters pageNo and numOfRows have no descriptions. The description merely repeats the required parameters without adding additional meaning or format details, and fails to explain the undocumented pagination parameters.

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 retrieves officetel (오피스텔) jeonse/wolse actual transaction prices, and specifies the required inputs (region code and contract year month). This distinguishes it from siblings like get_offi_trade (officetel sales) and get_apt_rent (apartment rent).

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 explicit guidance is given on when to use this tool versus its siblings. The description only states the tool's function without mentioning use cases, alternatives, or exclusions.

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