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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds valuable context: it states the response structure (summary, distribution, complexes, jeonse_ratio, insights) and the cost of 50 points per call, which goes beyond what annotations provide. However, it does not mention pagination behavior or data freshness.

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 front-loaded with the purpose and metrics, followed by response structure and cost. It is generally efficient, though the bilingual English/Korean repetition adds slight redundancy. Every part serves a purpose, but the duplication costs a perfect score.

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 six parameters and no output schema, the description does well to list the response keys (summary, distribution, complexes, jeonse_ratio, insights) and describe the computed metrics. It could be more complete by detailing what each response section contains, but it provides enough for an agent to understand the tool's scope and outputs.

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 100%, with all six parameters documented including examples and defaults. The description implies filtering by region and month (법정동코드, 계약년월) and mentions the jeonse_ratio comparison tied to includeTrade, but it does not add syntax, constraints, or other meaning beyond the schema. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 states a specific verb (analyze) and resource (Korean rent transactions) and enumerates the exact metrics computed: jeonse share, deposit/monthly-rent bands, annual-rent-to-deposit ratio, renewal share, and jeonse ratio. This clearly differentiates it from the sibling rtms_trade, which deals with sale transactions, even without naming it.

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 purpose implies when to use it (for rent market analysis), but there is no explicit guidance on when to choose this over rtms_trade or other real-estate tools, nor are there any exclusions or prerequisites. Usage is left to inference from the description and title.

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