taiwan_drug_info

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

No annotations are provided, so the description must disclose behavioral traits. It states the data source and what information is returned, but lacks details on error handling (e.g., invalid license number) or any restrictions.

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 concise, using two sentences to cover purpose, data source, and a suggestion for prior use. No unnecessary information, but the list of fields could be more structured.

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?

Given the simple query nature with one parameter and no output schema, the description adequately explains what the tool returns (list of fields). It mentions the data source, making it contextually complete for typical use.

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 input schema covers the single parameter 'license_no' with a description of its format and source. The tool description does not add additional semantic value beyond the schema, so performance is adequate.

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 clearly states the tool's purpose: querying drug details using a license number. It lists specific fields like active ingredient, indications, usage, etc., and distinguishes from sibling tool 'taiwan_drug_search' by stating the input source.

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 provides a clear usage flow: use 'taiwan_drug_search' first to obtain the license number. It does not explicitly exclude alternative uses, but the context is sufficient for an agent to understand when to invoke this tool.

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