search_tfda_drug

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

With no annotations, the description adds some behavioral context: the agent must treat structuredContent as source of truth and not infer missing facts. However, it does not disclose rate limits, auth needs, or destructive potential, leaving gaps.

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?

Two sentences, front-loaded with purpose. Every sentence adds value—purpose and handling contract. No wasted words.

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 lacks usage examples, parameter explanations, and context for when to invoke. Agent has limited guidance beyond the purpose statement.

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?

At 40% schema description coverage, the description fails to explain key parameters like query, limit, and search_type beyond their names. It adds no meaningful guidance over the schema.

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?

Clearly states the tool searches the Taiwan TFDA drug database for permits and product information. This distinguishes it from siblings like search_drug or get_drug_info by specifying the TFDA Taiwan scope.

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 includes an 'Agent contract' about handling output, but does not specify when to use this tool versus alternatives (e.g., when to prefer search_drug or get_drug_info). No explicit context for choosing this tool.

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