realestate_search_apt_trade

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

Annotations already declare this as read-only, idempotent, and non-destructive. The description adds useful constraints (e.g., year_month or start/end required, response_format default) that are not enforced by the schema. No contradictions with annotations exist.

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 compact and well-organized as a parameter list, with each line earning its place. It avoids fluff while covering all 8 parameters, though a brief note about return value could improve it.

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's complexity (8 parameters) and that an output schema exists, the description adequately covers all parameter semantics and key constraints. Sibling differentiation could be more explicit, but the purpose is clear enough for an agent to select correctly.

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 provides only parameter titles with no descriptions, so the Args list in the tool description fully compensates by explaining each parameter with examples, including the conditional requirement for date inputs. This adds high value over the structured 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 the tool queries 'apartment sales actual transaction prices' for specific regions/periods. This distinguishes it from sibling tools like realestate_search_apt_rent, which handles rentals, and analysis tools like realestate_analyze_price_trend.

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 implies usage when apartment sales data is needed but does not explicitly contrast with alternatives like rental search or analysis tools. The requirement that year_month or start/end is mandatory is a parameter guideline, not a when-to-use statement.

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