realestate_get_apt_summary

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the temporal scope ('최근 N개월' = recent N months) and response format options, providing some behavioral context, but does not disclose return structure or edge cases.

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 concise single sentence in Korean followed by an Args list. It front-loads the core action and includes necessary parameter constraints without any fluff or redundancy.

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 an output schema exists and annotations cover read-only behavior, the description is mostly complete: it defines the scope (specific complex, time range, output format). However, it lacks guidance on selecting this over related tools, making it slightly incomplete for full contextual understanding.

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 coverage is 0%, so the description carries the burden. It explains all four parameters: region, apt_name, months with default and max, and response_format with default. This adds meaning beyond the bare schema names, though it lacks examples or valid value enums.

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 provides comprehensive summary information for a specific apartment complex, using a specific verb and resource. It differentiates from siblings like search_apt_trade or analyze_price_trend by focusing on 'specific complex summary', though it does not explicitly name alternatives.

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 given on when to use this tool versus alternatives like realestate_search_apt_trade or realestate_analyze_price_trend. The description only explains what the tool does, implying usage for summary queries but lacking explicit scenarios, exclusions, or comparisons.

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