get_transport_requirement

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It offers metadata flags like 'decision_support_only=true' and 'not_validated_for_hospital_deployment=true', which hint at constraints, but it does not describe what the tool does, what it returns, or what side effects or permissions apply.

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 poorly structured: the '=true' flags read like serialized metadata rather than coherent guidance, and the Chinese privacy warning is appended without context. It is not overly long, but the limited space is spent on opaque flags instead of useful tool semantics.

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?

Even with only one parameter and an output schema, the description omits the core purpose and input semantics, leaving an agent unable to confidently decide whether this is the correct tool among many similar sibling tools. The constraint flags add some context but do not make the definition complete.

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%, and the description does not mention the 'disease' parameter at all. The agent must rely solely on the parameter name, with no information about accepted values, format, or expected input.

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 never states that this tool retrieves transport requirements for a disease; 'CDC compatibility alias' is an opaque label that does not explain the tool's function. It relies on the tool name for meaning and lacks a clear verb and resource description.

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 siblings like get_specimen_requirement or get_collection_method. The Chinese instruction '不得輸入病人資料' ('do not input patient data') is a constraint, not a usage scenario, and no alternatives or exclusion conditions are mentioned.

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