get_collection_method

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

No annotations are provided, so the description carries the full burden. It does disclose several behavioral flags (decision_support_only, verify_current_official_source, not_validated_for_hospital_deployment, not_pre_submission_storage) and the patient-data restriction, which gives some context beyond what structured fields would provide. However, these flags are cryptic and unexplained, and the description does not mention what the tool returns or any side effects, so the disclosure is incomplete.

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 short, but it is not well-structured. It opens with a cryptic 'CDC compatibility alias' and then lists unformatted flags followed by a Chinese sentence. It does not front-load the primary purpose, and the information provided is dense but not organized for quick comprehension.

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?

Despite having an output schema, the description gives no indication of what the tool returns or how it fits into the overall workflow. With a single parameter and no explanation of its purpose or behavior, the description is severely incomplete for an agent to decide whether and how to invoke it 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?

Schema description coverage is 0%, so the description must explain the 'disease' parameter. It does not state what values are valid, what format is expected, or how to provide it. The only relevant hint is 'do not input patient data,' which is a negative constraint but not a semantic explanation of the parameter's meaning or domain.

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 says 'CDC compatibility alias' which is vague and does not state a specific action or resource. It does not explicitly say it retrieves collection methods for a disease, and the name 'get_collection_method' is only partially echoed. It reads more like a label than a purpose statement, leaving the agent to guess what the tool actually does.

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?

There is no guidance on when to use this tool versus any of the 21 sibling tools. The only usage hint is the Chinese sentence '不得輸入病人資料' (do not input patient data), which is a constraint on input content, not a selection criterion. No alternatives or exclusions are mentioned.

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