특정 병원의 비급여 목록

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

With no annotations, the description carries the full behavioral disclosure burden. It transparently reveals a key limitation: no server-side ykiho filter, so matching is done client-side by narrowing with hospital name and region. This is meaningful behavioral context beyond the schema, though it could also mention pagination behavior.

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 two concise sentences, front-loaded with the primary purpose in the first sentence and supplementary limitation/source in the second. Every word earns its place with no redundancy or filler.

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?

For a 5-parameter lookup tool with no output schema, the description provides adequate context: hospital-specific scope, matching limitation, and data source. The format parameter in the schema covers return value semantics. It stops short of a 5 because pagination behavior and potential edge cases like multiple hospitals with the same name aren't addressed.

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%, so all five parameters are already documented. The description reinforces the region parameter's role in narrowing results but adds little new meaning beyond what the schema already states. Baseline 3 is appropriate when the schema does the heavy lifting.

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 non-payment items and prices for a specific medical institution by hospital name (기관별 목록). This is a specific verb+resource that distinguishes it from sibling tools like kohealth_search_nonpayment, which likely performs broader searches.

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 provides practical guidance by noting that there is no ykiho server filter, so users should combine hospital name with region to narrow matching. This implies when to use region and improves search accuracy, though it doesn't explicitly contrast with alternative sibling tools.

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