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

With no annotations the description carries full burden, and it discloses useful operational traits: open_now is judged server-side in Korean time, and every result carries per-day hours, phone and coordinates. It omits auth/rate-limit details, but for a public read-only dataset lookup the essential behavior is covered.

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?

Four short sentences: capability, source, filter usage, and return contents, in that order. Nothing is wasted and the most decision-relevant information is front-loaded.

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?

Without an output schema the description still explains what each result contains (hours, phone, coordinates). Filters beyond open_now/day (region, kind, emergency) are left to the schema, which documents them adequately, so nothing critical is missing.

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 100%, so baseline is 3; the description adds real meaning by clarifying that open_now is a server-side KST determination rather than a client-side clock check, and demonstrates the day enum with day='sun'.

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?

Starts with a specific verb and resource (제주 병의원·약국 검색) and adds scale and provenance (국립중앙의료원 공공데이터). An agent immediately knows this finds medical facilities in Jeju, and no sibling tool overlaps.

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?

Gives concrete usage for the key filters: open_now=true for 'currently open' and day='sun' for Sunday clinics, each with a worked example. There are no alternative tools to route against, so no when-not guidance is needed.

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