doc_opd_patient_list_previous

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

With no annotations, the description carries the full burden. It discloses a key behavioral limitation (date restriction) and an internal conversion (auto-formatting to YYYYMMDD), plus lists return fields. These insights go beyond the bare schema.

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 with clearly labeled sections: purpose, caveat, args, returns, and internal conversion. Every sentence contributes, with no redundant fluff.

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?

The description covers core behavior, return fields, and date constraints, but leaves ambiguity around whether 'date' and 'date_start/date_end' are mutually exclusive, and fails to explain the required eip_id/eip_password parameters. Adequate but with clear gaps.

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 description adds meaningful semantics for date, date_start, and date_end with format and example, but it entirely omits eip_id and eip_password, which are required. Given 0% schema coverage, this partial compensation is insufficient for the auth parameters.

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 opens with '取得醫師過去看診名單' (retrieve doctor's past outpatient visit list), which clearly states the tool's verb and resource. The note '僅能查詢過去日期' reinforces the 'previous' scope, distinguishing it from appointment-related siblings like doc_opd_patient_list_appointment.

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 explicitly states when the tool can and cannot be used: only past dates are queryable; today or future dates return no data. This provides clear usage context, though it does not mention alternative tools for future or appointment queries.

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