get_officetel_rent

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

No annotations are provided, so the description carries full burden. It lacks behavioral context such as idempotency, rate limits, authorization needs, or side effects. Return format is detailed, but behavioral traits are missing.

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?

Well-structured with separate sections for purpose, args, and returns. Front-loaded with main action. Could be slightly more concise, but overall efficient.

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 presence of an output schema (though not shown), the description fully documents return fields, includes error/network failure handling, and covers default behavior. Complete for a data-retrieval 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?

Schema description coverage is 0%, but the description fully compensates: explains region_code as a 5-digit legal district code returned by get_region_code, year_month in YYYYMM format with example, and num_of_rows with default. Adds clear meaning beyond the schema.

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 it returns officetel lease and monthly-rent records for a region and month, with specific verb 'Return'. It distinguishes from siblings like get_officetel_trades and other property-specific rent tools.

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?

Provides explicit usage guidance: use alongside get_officetel_trades to compute jeonse ratio and evaluate rental yield. Advises calling get_current_year_month if year_month not specified. However, no explicit when-not-to-use or alternatives for other property types.

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