获取病历/报告结构化资料

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

无注释，描述仅提及默认不返回OCR文本，但未说明includeText=true时的具体行为（如是否返回全文、大小限制等），也未提及只读性、权限需求或错误处理。

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?

两句中文，核心信息在前，无冗余。有效传达了工具用途和关键行为。

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?

无输出schema，无注释，参数说明不完整。虽然核心用途清晰，但缺少返回结构描述、使用前提等关键信息。

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?

描述了includeText参数的默认行为，但未解释documentId参数的含义或格式。schema覆盖率0%，描述部分弥补但不够完整。

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?

明确指定动词'获取'和资源'单份病历/报告的结构化资料'，且通过'单份'的限定区分了同组的health_document_list。默认行为说明进一步澄清了工具特性。

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?

未明确说明何时使用此工具而非其他同组工具（如health_document_export或health_document_ingest），也未提供使用禁忌或前提条件。

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